Skip to main content
Concept guide · ISO 26262 + ISO 21448 · 14 chapters

Perception System Safety

Engineer the subsystem the planner has to trust: requirements derived from hazards, a pipeline whose failures wear disguises, a contract that states its negative promises, and evidence that survives a skeptic.

Chapters
14
Chapters
Pipeline stages
8
Pipeline stages
Monitor classes
5
Monitor classes
Assurance perspectives
4
Assurance perspectives
Included inExpert
The short version

Quick answers

What is perception system safety in ISO 26262 terms?
It is the treatment of the perception subsystem as a safety-relevant engineered element rather than a machine-learning research problem. The subsystem begins where an interface-valid sensor measurement exists and ends where the environment model is published, and the requirements attached to that boundary are derived from vehicle-level hazardous events. ISO 26262 governs the part where malfunctioning behaviour of the E/E system causes hazards: memory corruption in a tracker, a failed imager region, a missed inference deadline, a monitor whose reaction chain does not fire in time. The guide keeps that scope explicit and shows where it stops.
How do ISO 26262 and ISO 21448 divide perception failures between them?
ISO 26262 addresses hazards caused by malfunctioning behaviour of E/E systems, so hardware faults, systematic software faults, timing violations and the faults of a monitor implementation belong to it. ISO 21448 addresses unreasonable risk from functional and performance insufficiencies and their triggering conditions, excluding faults already covered by ISO 26262: a radar multipath ghost produced with no E/E fault, or a camera that is simply insufficient in fog. The scopes overlap rather than partition cleanly. A fog case, for example, can be a SOTIF triggering condition exposing an insufficiency while the implemented condition monitor and its reaction chain remain within the malfunction-oriented scope. The guide routes eight worked cases with the reasoning for each.
Why this course · ISO 26262

Why it pays for itself

Requirements you can defend, not benchmark scores

Follow the derivation from a hazardous event at the bumper through braking physics to measurable perception requirements with classes, ranges, latencies, conditions and separate budgets for misses and false alarms.

Know which standard owes which evidence

Eight concrete perception failures routed across ISO 26262, ISO 21448, ISO/PAS 8800 and ISO/SAE 21434, so a fog case, a memory bit flip and a crafted sign each produce the right kind of evidence instead of the same argument three times.

An architecture argument, not a sensor shopping list

Fusion topologies compared on fault reachability, an environment model specified as a contract with negative promises, and a monitoring portfolio whose blind spots are named and carried into the residual-risk statement.

After the course

What you’ll be able to do

Derive Perception Requirements Instead of Inheriting Them

Trace vehicle hazards and braking physics down to measurable subsystem requirements with explicit classes, ranges, latencies, conditions and error budgets, and stop treating a benchmark score as a requirement.

Route Every Failure to the Right Assurance Perspective

Separate ISO 26262 malfunctions from ISO 21448 performance insufficiencies, ISO/PAS 8800 AI concerns and ISO/SAE 21434 threats, and recognise the cases where several perspectives apply at once.

Choose a Fusion Architecture With Your Eyes Open

Compare object-level, low-level and hybrid wirings on fault reachability, observability and what remains checkable, and identify the double counting and covariance inconsistencies that inflate confidence.

Specify the Environment Model as a Contract

Write semantics, units, frames, timing, uncertainty meaning and negative promises for every field, and treat misreadings such as absent-versus-unknown collapse as a failure class rather than a bug tracker entry.

Build a Monitoring Portfolio and Declare Its Blind Spots

Map failure modes against monitor classes with firing latencies, decide which detections can support a safety mechanism, and name the failures that stay silently plausible instead of hiding them.

Assemble Perception Evidence That Survives Review

Combine open-loop and closed-loop evidence, size rare-event claims honestly, report per-slice results, and structure the whole thing into a safety-case fragment whose residual risk is stated rather than implied.

The curriculum · 14 chapters

Chapter by chapter

  1. 01

    What Perception Owes the Planner

    The uncomfortable starting fact: there is the physical world and there is the published environment model, and the planner lives entirely in the second one. Where the subsystem boundary sits, why a benchmark score is not a safety requirement, and the highway reference function that every later chapter traces back to.

    • Two worlds, one interface
    • Subsystem boundary
    • Benchmarks versus requirements
  2. 02

    Four Ways of Seeing

    Camera, radar, lidar and ultrasonic as four pieces of physics with four different ways of being wrong. Angular sampling against lane width, geometric support that thins with range, and a modality by condition matrix that shows which weather hurts which sensor.

    • Modality physics
    • Angular resolution
    • Condition matrix
    • Limits of complementarity
  3. 03

    From Vehicle Hazards to Perception Requirements

    The derivation chain walked end to end: hazardous events at the vehicle, safety goals, braking physics, a required perception range, then measurable subsystem requirements. Why a missed object and a phantom object are separate hazardous-event paths with separate budgets that must never be traded silently.

    • HARA to safety goal
    • Required perception range
    • Separate miss and false-alarm budgets
  4. 04

    Four Standards Perspectives, One Pipeline

    Route a perception failure before you fix it. How ISO 26262 malfunctions, ISO 21448 performance insufficiencies, ISO/PAS 8800 AI concerns and ISO/SAE 21434 threats apply to the same pipeline, where their scopes overlap, and why the routing decides which evidence you owe.

    • Four overlapping scopes
    • Routing worked cases
    • Evidence follows the routing
  5. 05

    The Pipeline: From Photons to a Published World

    Eight processing layers between a photon and the model the planner reads, each holding state and each failing in a distinctive downstream disguise. The confirmation logic that dominates the latency budget, and why an object list that stays silent about unobserved space is a design error, not a shortcut.

    • Eight stages and payloads
    • Failures wear disguises
    • The confirmation trade
    • Unknown is not free
  6. 06

    Fusion Architectures and What They Do to the Safety Argument

    Object-level, low-level and hybrid fusion compared on what they cost the safety argument rather than on accuracy. How far one sensor fault travels in each wiring, the failure modes fusion invents including double counting, and why overconfident covariance quietly shrinks a planner safety margin.

    • Three topologies
    • Fault reachability
    • Double counting
    • Diversity you can defend
  7. 07

    The Environment Model Is a Contract

    The handover from perception to planning treated as a specified interface rather than a message with fields: semantics, units, frames, timing, and a statement of what each value may be relied upon for. The negative promises matter most, and contract violations form a failure class of their own.

    • Field-by-field semantics
    • Standardized versus project interfaces
    • Negative promises
    • Per-sector range claims
  8. 08

    Uncertainty a Planner Can Act On

    Why a ranking score and a calibrated probability are different promises, and what happens when a consumer mistakes one for the other. Existence, state and class uncertainty each drive a different planner lever, and noise that averages away is not the same as ignorance that does not.

    • Scores versus probabilities
    • Calibration diagnostics
    • Three uncertainties, three reactions
    • Aleatoric versus epistemic
  9. 09

    Time, Frames and Calibration

    Every measurement is a value, a coordinate frame and a time, and corrupting any of the three places a perfectly correct value in the wrong world. Timestamp skew, extrinsic drift that grows with range, the transform chain and its owners, and freshness as a field the consumer must check.

    • Coherent, not random, errors
    • Time skew
    • Drift with range
    • Freshness as a promise
  10. 10

    Degradation Without Failure

    Six ways to see less with nothing broken: blockage, contamination, weather, glare, mutual interference and simply leaving the validated envelope. Why the stack must estimate and publish its own reach, and how availability pressure on suppression thresholds pushes one safety budget against another.

    • Degradation without fault codes
    • Estimating your own reach
    • The suppression see-saw
    • Edge of the validated world
  11. 11

    Monitors, Diversity and the Simple Channel That Says No

    Perception cannot self-certify, because the estimate and the estimate of its quality fail together. Five monitor classes with their characteristic blindness and speed, a coverage matrix that doubles as a specification tool, the doer and checker pattern, and the silent set nobody catches in time.

    • Five monitor classes
    • Coverage matrix
    • Doer and checker
    • Naming the silent set
  12. 12

    Degraded Modes and the Perception Bench

    Between driving at full speed while blind and braking for every doubt sits an engineered ladder of partial function, entered on declared capability and health rather than on fault codes. Asymmetric transitions, hysteresis and debounce, and a bench that wires the whole page together so failures can be injected against it.

    • Health-driven mode ladder
    • Hysteresis and debounce
    • Injecting failures on a bench
  13. 13

    Building the Perception V&V Evidence

    What each layer of evidence can honestly claim, from open-loop replay through re-simulation and scenario exploration to road driving. The arithmetic of rare events, why slice metrics must come before averages, and how field monitoring keeps the argument current after start of production.

    • Open loop versus closed loop
    • Rare-event arithmetic
    • Slices before averages
    • Field monitoring loop
  14. 14

    A Worked Safety-Case Fragment

    One perception requirement argued end to end in goal-structuring form, with context, strategy and solution nodes drawn from the analyses the earlier chapters built. The residual-risk statement written out loud, why a safety case goes stale rather than wrong, and an honest account of what the fragment does not show.

    • Argument assembled from evidence
    • Residual risk stated openly
    • Change impact and staleness
Built for

Who this guide is for

  • Perception and sensor-fusion engineers moving from accuracy metrics to safety requirements
  • Safety engineers who must review a perception subsystem they did not build
  • System architects deciding sensor sets, fusion topology and degraded-mode strategy
  • Verification and validation leads planning perception evidence campaigns
  • Assessors and reviewers reading a perception safety case for the first time

Frequently Asked Questions

Common questions about Perception System Safety

Because the handover from perception to planning is an interface between two engineering organizations, and every field of it is a promise. Object identity, class taxonomy, pose and velocity conventions, covariance consistency, existence probability and its calibration, track age, sensor provenance, free-space state, per-sector range validity, health flags and timestamps each have at least one documented way of being misread. Misreadings are a failure class of their own: both sides can be internally consistent under different assumptions while vehicle behaviour is still wrong. The guide treats units and frames, score-versus-probability drift, absent-versus-unknown collapse, enum drift and timestamp semantics as interface analysis and verification items.
Less than the word suggests, unless its coverage and its deadline are both established. Perception cannot self-certify because the estimate and the estimate of its quality are computed by the same machinery: a filter with an unmodelled bias reports a narrow covariance, and a detector blinded by glare reports no objects with no alarm. The guide sorts monitors into input-integrity, statistical, cross-modality plausibility, model-based plausibility and operating-condition classes, each with a characteristic blindness and a characteristic latency, then builds a coverage matrix that doubles as a specification tool. A detector becomes part of a safety mechanism only when its requirement, reaction, timing and coverage are specified and verified.
Enough that the number of eligible independent encounters, not the raw frame count, carries the claim. The guide works through the zero-event binomial bound and its rule-of-three approximation, so a per-encounter target tightened by a factor of ten costs roughly ten times as many clean encounters under the same assumptions. It also separates open-loop replay, which is statistically powerful but blind to consequences, from closed-loop evaluation, which can tell an error the planner absorbs apart from one that reaches the bumper, and shows why per-slice results must be reported before an exposure-weighted average hides the low-exposure cells where hazards live.
The course has 14 chapters: what perception owes the planner, the four sensing modalities and their failure physics, the derivation from vehicle hazards to perception requirements, the four assurance perspectives routed across one pipeline, the eight-stage pipeline and its failure disguises, fusion architectures and their effect on the safety argument, the environment model as a contract, uncertainty a planner can act on, time and frames and calibration, degradation without failure, monitors and diversity and the simple checking channel, degraded modes and the perception bench, building the verification and validation evidence, and a worked safety-case fragment with its residual-risk statement. A single highway reference function runs through all fourteen chapters, and its numbers are illustrative teaching values rather than product data.

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.