ISO 21448: Scenario Databases and Tooling — Building the Scenario Asset Your Whole Program Reuses

Date
2027-06-14
Location
Online
Host
Zach L
Register

About this event

A live 30-minute expert session on Scenario Databases and Tooling — Building the Scenario Asset Your Whole Program Reuses (ISO 21448 — Safety of the Intended Functionality). What We'll Cover: Why a governed scenario database is the backbone asset of an ISO 21448 program and which lifecycle activities read and write it The build method step by step: schema design (ODD tags, triggering conditions, area classification), ASAM OpenSCENARIO and OpenDRIVE ingestion, versioning and review workflow How the database maps to ISO 21448 work products, exporting the known-scenario catalog and validation coverage reports on demand Common mistakes: scenarios without ODD or triggering-condition metadata, uncontrolled edits breaking test reproducibility, sim-only formats blocking track reuse The evidence auditors expect: version-controlled scenarios, change history, and queries reproducing exactly what was tested for a given release Related topics: scenario database · openscenario · opendrive · asam openx · scenario metadata · scenario management tooling · version control scenarios · scenario reuse · test reproducibility · scenario schema · database governance · scenario ingestion · coverage query · release baseline Critical Systems Analysis provides embedded functional safety consulting for ISO 21448 — Safety of the Intended Functionality. Learn more: https://criticalsystemsanalysis.com Partner with us: https://meetings.hubspot.com/benjamin-twombly/strategic-partnerships

Topics

About Functional Safety Foundations

This online session delivers expert-led instruction on the regulatory landscape and implementation approach for Functional Safety Foundations.

The cross-sector fundamentals underlying every functional safety standard: risk as severity × likelihood, the safety function concept, integrity levels, the safety lifecycle, and the split between random and systematic failures.

What it regulates

Shared vocabulary and reasoning: hazard → risk → risk reduction allocation → safety requirement → verified implementation → maintained integrity in operation.

Who must comply

Everyone entering the field — the conceptual base of the entire catalog.

Key requirements of Functional Safety Foundations

  • Hazard and risk fundamentals
  • Safety function anatomy: sensor-logic-actuator with defined safe state
  • Integrity ladders (SIL/PL/ASIL/DAL) as risk-reduction currencies
  • Random vs systematic failure treatment
  • Lifecycle and management of functional safety incl. competence

Key concepts: Functional Safety Foundations

Functional safety management
Planning, competence, documentation and assessment wrapped around technical work.
Random vs systematic
Hardware wear-out/chance failures quantified statistically versus design/process errors controlled by rigor.
Risk reduction allocation
Distributing required risk reduction among mechanical design, safeguards, control functions and procedures.
Safe state
The defined condition a function drives the equipment to on demand or fault.

Frequently asked questions: Functional Safety Foundations

Why can't testing alone prove safety?

Rare-event targets (like 1e-7/h) are unverifiable by test duration, and systematic errors evade random testing — hence the standards' dual machinery of quantified hardware analysis plus process rigor and independent assessment.

Standard information based on the published text of Functional Safety Foundations. Event content is provided by the host. For authoritative guidance, consult the official standard body.