Contents

SOTIF and AI safety

Safety of the intended functionality — hazards that arise even when nothing is broken, for example when a camera-based system misreads a scene — and how ISO 21448 and ISO/PAS 8800 address them.

1 min read · Discipline stake: Safety Software Architecture Hardware

Why it exists

ISO 26262 deals with faults. But an automated emergency braking system can also cause harm when it works exactly as designed — for example when it misinterprets a shadow as an obstacle. These are functional insufficiencies.

What SOTIF covers

  • Triggering conditions: situations that lead to hazardous behaviour (glare, unusual objects).
  • Known and unknown unsafe scenarios: reduce both through analysis, simulation and testing.
  • Validation: argue that the residual risk is acceptable.

ISO/PAS 8800 extends this to AI: data quality, model development, training and monitoring in operation.

Best practices

  • Combine scenario-based simulation with field data to discover unknown unsafe scenarios.
  • Define the operational design domain precisely.

Common pitfalls

  • Treating SOTIF as a testing activity only, without design measures.

What it means for your discipline

  • Functional safety Core

    Identifies triggering conditions and functional insufficiencies, and argues residual risk.

  • HPC & application software Core

    Perception and decision software, including machine-learning models, are the main sources of functional insufficiencies.

  • E/E architecture Partial

    Sensor diversity and fallback architectures reduce SOTIF risks.

  • Hardware & silicon Partial

    Sensor performance limits (range, weather) define the operating envelope.

No direct stake: Cybersecurity · Base software · Networks & communication · Diagnostics & lifecycle · Software update & OTA

Where it sits in the software stack

Generic layered software of a central HPC (application processor with hypervisor, plus a safety island) and of a classic MCU-based ECU (AUTOSAR Classic). Highlighted modules matter for this topic. Click any module to open its page.

HPC · application processor (MPU) and safety island (MCU)
  • ADAS functions — Perception and planning must handle sensor limitations, recognize operating limits and avoid hazardous decisions in triggering conditions.
MCU-based ECU · AUTOSAR Classic
  • Application layer — Driver assistance components must handle functional insufficiencies and implement fallback behavior when operating limits are reached.