Robots Atlas>ROBOTS ATLAS
Safety

Safety-Critical Autonomous Systems (SCAS)

2001ActivePublished: 16 June 2026Updated: 16 June 2026Published
Key innovation
Integration of classical functional-safety engineering (ISO 26262, DO-178C, IEC 61508) with AI systems, where lack of deterministic behavior and full provability requires new methods of validation, runtime monitoring, and safe-fail mechanisms.
Category
Safety
Abstraction level
Paradigm
Operation level
SystemRobot controlDeploymentEvaluation (runtime)
Use cases
Level 3+ autonomous vehicles (Waymo, Cruise, Mobileye)Unmanned aerial vehicles (UAVs) operating in public airspaceSurgical robots (da Vinci) and autonomous medical devicesCollaborative industrial robots (cobots) and automated production linesRailway safety systems (ETCS, automated metro driving)Autonomous defence systems and weapons (LAWS, "human-in-the-loop")Humanoid robots operating near humans (Apptronik, Figure, Optimus)

How it works

SCAS architecture is layered. (1) Perception layer: redundant, diverse sensors (RGB cameras, LiDAR, radar, IMU) โ€” no single modality is a critical point of failure. (2) AI/ML layer: the main decision stack (planner, perception, prediction) uses deep models, but its outputs are always observed. (3) Runtime monitoring layer: OOD detectors, uncertainty monitors (epistemic + aleatoric), statistical model checking, safety-predicate evaluation (e.g. "speed < limit", "distance > minimum"). (4) Safety cage / simplex layer: a deterministic backup controller that can take over if AI behaves anomalously or enters an undefined state โ€” e.g. stop the vehicle, return manual control to the pilot, alert the operator. (5) Validation: combination of classical methods (HIL testing, millions of km/hours of field testing) with new AI-specific techniques (adversarial testing, scenario-based testing, fuzz testing, formal verification of critical components). (6) Certification: documenting the evidence chain in line with industry standards and new ones (ISO 21448 SOTIF, ISO 8800, EU AI Act Annex III).

Problem solved

Classical functional-safety methods do not directly apply to AI systems: one cannot prove correctness of neural-network weights, there are no deterministic error bounds, and behavior on out-of-distribution inputs is unpredictable. SCAS addresses the question: how to introduce AI into systems whose failure can kill, while preserving the level of rigor required by standards and regulators.

Components

Safety cage / Simplex architectureLast line of defense โ€” guarantees the system stays safe even under unpredicted AI behavior.

A deterministic supervisor controller that observes AI outputs and can take over when behavior leaves the safety envelope. The simplex architecture (Sha 2001) โ€” a simple, provably correct fallback controller alongside a complex but non-deterministic AI controller.

Runtime monitoringBridge between AI and classical safety engineering โ€” translates "weird model behavior" into deterministic signals.

Continuous evaluation of safety predicates, epistemic uncertainty, input-distribution drift (OOD detection), and consistency of outputs with the nominal model. Generates escalation signals to the supervisor layer.

Official

Redundancy and diversityIncreases MTBF (mean time between failures) and detects systematic, common-cause failures.

Multiple independent decision stacks (e.g. two planning systems built on different models), diverse sensors, and independent actuation paths. Eliminates single points of failure (SPOF).

Official

Formal verification of safety predicatesHard mathematical foundation for certification.

Provable verification of critical safety properties (e.g. "the car never enters an intersection on red") using model checking, SMT solvers, or theorem provers. Applied to deterministic layers, not the network itself.

Official

Certification & standards complianceNecessary condition for market entry in regulated domains.

Compliance with industry standards: ISO 26262 (ASIL Aโ€“D), ISO 21448 (SOTIF โ€” safety of the intended functionality), ISO 8800 (AI in automotive), DO-178C / DO-254 (aviation), IEC 61508 (SIL 1โ€“4 industrial), IEC 62304 (medical). Plus EU AI Act for high-risk systems.

Implementation

Implementation pitfalls
Distribution shift at deploymentCritical

The production environment contains scenarios absent from training (rare weather, unusual road situations, mud-covered sensors). AI loses confidence or produces wrong predictions.

Fix:OOD detection, data augmentation, scenario-based testing, continuous performance monitoring, fast retraining cycle, conservative fallback mechanisms.
Common-cause failures in redundancyHigh

Two "independent" decision stacks can fail simultaneously due to the same cause โ€” e.g. both use the same library, training data, or backbone network.

Fix:Enforced diversity (diverse implementation): different languages, architectures, datasets. Redundancy audits.
Insufficient edge-case dataHigh

The most dangerous scenarios (accidents, extreme conditions) are inherently rare. The dataset has strong imbalance โ€” the model mostly learns "nominal" scenarios.

Fix:Synthetic simulation (Waymo, NVIDIA Omniverse), data augmentation, active learning, scenario libraries (PEGASUS, OpenScenario).
Late escalation to fallback layerCritical

Runtime monitor detects the problem too late; the simplex layer cannot stop the system before consequences materialise.

Fix:Conservative monitor thresholds, redundant monitors (sensor + behavioral + statistical), reachability analysis to compute safe decision margins.

Evolution

Original paper ยท 2001 ยท IEEE Software (Simplex architecture as the foundation of modern SCAS) ยท Lui Sha
Using Simplicity to Control Complexity
Lui Sha
1986
Therac-25 โ€” tragic catalyst
Inflection point

Therac-25 radiation therapy failures killed patients due to software errors, exposing the inadequacy of classical software engineering in safety-critical systems and forcing the field to develop.

1998
IEC 61508 โ€” first horizontal functional-safety standard

First standard defining SIL (Safety Integrity Level) tiers and a framework for electrical/electronic/programmable systems. Became the template for industry-derived standards.

2001
Simplex Architecture (Sha)
Inflection point

Lui Sha proposes the formal safety-cage architecture โ€” a simple, provably correct controller alongside a complex non-deterministic one. The architectural foundation of modern SCAS.

2011
ISO 26262 โ€” automotive functional safety

Launch of the automotive standard with ASIL Aโ€“D levels. Became the industry standard for every carmaker and gave rise to a whole ecosystem of tools and processes.

2018
Uber crash in Tempe โ€” the SCAS frontier
Inflection point

Pedestrian Elaine Herzberg died after being struck by an Uber autonomous car. Investigation revealed the AI system "dismissed" a real object as a false positive and the human operator was not ready to take over. Inflection point in the discussion about SCAS for cars.

2019
ISO 21448 (SOTIF)

Standard complementing ISO 26262 with "Safety Of The Intended Functionality" โ€” addresses the safety of correctly functioning features under uncertainty (e.g. AI perception in unusual weather).

2024
EU AI Act and ISO 8800
Inflection point

Introduction of the EU AI Act (high-risk AI systems regulation) and ISO 8800 specific to AI in automotive. First serious regulatory and normative framework for AI/ML-based SCAS.

2025
Commercial robotaxi (Waymo) and humanoids in factories

Waymo scaled commercial robotaxi service in several US cities, and humanoids (Figure 02, Apptronik Apollo) started working in BMW and Mercedes factories โ€” the first cases of largely-neural-network SCAS in commercial services.

Hyperparameters (configurable axes)

Safety integrity level (SIL/ASIL)Critical

Required level of rigor per industry standard. Affects development process, redundancy, audit frequency, and allowed failure rate (1e-9 / hour for DAL A in aviation).

ASIL DHighest automotive level (ISO 26262) โ€” e.g. steering.
DAL AHighest aviation level (DO-178C) โ€” catastrophic failure.
SIL 4Highest industrial level (IEC 61508) โ€” below 1e-8 / hour.
Fallback modeCritical

What the system does when the safety monitor detects an anomaly. The specific mode depends on the domain โ€” a car can pull over, an aircraft can hand control back to the pilot, a robot can freeze.

Minimal Risk Maneuver (MRM)Standard in autonomous cars โ€” pulling over.
Hand back to pilotAviation โ€” autonomy hands control back to a human pilot.
Safe stop / freezeIndustrial robots โ€” immediate motion stop.
Redundancy levelHigh

Number of independent decision paths. Higher redundancy increases MTBF and detects systematic errors but raises cost and complexity.

Dual-channel (1oo2)Standard for many SIL 2/3 use cases.
Triple modular redundancy (TMR)Avionics and aerospace โ€” 2-out-of-3 voting.

Execution paradigm

Primary mode
Conditional

The system switches between nominal mode (AI in charge), cautious mode (AI under strict monitoring), and emergency mode (deterministic fallback controller) depending on safety-monitor state.

Activation pattern
Input dependent

Parallelism

Parallelism level
Partially parallel

The main AI stack and runtime monitoring can run in parallel on different compute units. The simplex layer is a sequential supervisor; its overriding decision cannot be skipped due to latency.

Scope
Inference

Hardware requirements

Good fit

The main AI stack (perception, prediction, planning) runs on GPUs. Often automotive-certified GPUs are used (NVIDIA DRIVE).

Primary

The simplex / safety-cage / runtime-monitor layer typically runs on lockstep CPUs with hard real-time, for full provability.

Good fit

FPGAs are used for deterministic, verifiable sensor signal processing (LiDAR, radar) and as a platform for simplex.