Safety certification and V&V for autonomous systems

Scope and problem definition

Safety certification and verification & validation (V&V) for autonomous systems covers the evidence, standards, engineering methods, and regulatory processes used to show that an automated driving system (ADS), robotaxi, autonomous truck, or other autonomous machine is acceptably safe. The core difficulty is not only that hardware can fail, but also that the system may misperceive the world, plan an unsafe action, or encounter a scenario outside its design envelope without any component failure.

Phil Koopman and Michael Wagner framed the problem as an interdisciplinary challenge: autonomous vehicle safety must combine requirements engineering, system safety, software V&V, human factors, and regulatory policy, because a purely fault-based safety analysis cannot handle autonomy. Journal source:

• Koopman, P., & Wagner, M. (2017). “Autonomous Vehicle Safety: An Interdisciplinary Challenge.” IEEE Intelligent Transportation Systems Magazine, 9(1), 90–96. DOI: 10.1109/MITS.2016.2583491

The terminal risk is not merely component failure; it is a system that is functioning exactly as designed but is still unsafe in a particular operational scenario. That is why safety certification for autonomy is built around evidence-based safety cases, not just checklists.

Tier-1 standards and regulatory architecture

The strongest available sources in this domain are standards-body documents and regulator technical assessments.

2.1 ISO 26262: functional safety

ISO 26262 is the international standard for functional safety of electrical and electronic systems in road vehicles. The 2018 edition is the current full revision:

• ISO 26262-1:2018, Road vehicles — Functional safety — Part 1: Vocabulary, International Organization for Standardization. URL: https://www.iso.org/standard/68383.html

ISO 26262 uses Automotive Safety Integrity Levels (ASILs) from A through D. ASIL D is the most stringent. The standard requires hazard analysis, fault injection, derived safety requirements, safety mechanisms, and quantitative random-hardware-failure targets. However, ISO 26262 is weak for autonomy because it assumes hazards arise chiefly from malfunctioning behavior of electrical/electronic systems. It does not directly solve hazards caused by the system behaving as designed but with insufficient situational understanding.

2.2 ISO 21448: Safety of the Intended Functionality

The complementary standard is SOTIF:

• ISO/PAS 21448:2019, Road vehicles — Safety of the intended functionality, ISO. URL: https://www.iso.org/standard/70939.html
• ISO 21448:2022, published as a full standard in June 2022. URL: https://www.iso.org/standard/77490.html

SOTIF addresses hazards arising from functional insufficiencies, including sensor limitations, perception error, decision algorithm limitations, and unknown or unspecified operational situations. It requires a structured evaluation of known and unknown unsafe scenarios, validation targets, and residual risk. The transition from PAS 2019 to full IS 2022 is significant because it moved SOTIF from a preliminary specification to a normative international standard.

2.3 UL 4600: safety case for autonomous products

UL 4600 is the most autonomy-specific standard:

• UL 4600, Standard for Safety for the Evaluation of Autonomous Products, Edition 2, published 2022-02-24. Catalog URL: https://standardscatalog.ul.com/ProductDetail.aspx?productId=UL4600_2_20220224

UL 4600 requires a safety case: a structured, evidence-backed argument that the autonomous product is safe for its intended operational design domain. Unlike ISO 26262, UL 4600 explicitly includes autonomy-specific topics such as machine learning lifecycle, operational design domain boundaries, prediction of other road users, fail-operational behavior, and safety case deviations. It is not a functional-safety standard in the narrow fault-only sense; it is a safety case evaluation standard.

2.4 NHTSA crash reporting and testable scenario framework

The U.S. National Highway Traffic Safety Administration has two directly relevant technical regulatory instruments:

• NHTSA Standing General Order 2021-01, issued 2021-06-29, requiring manufacturers and operators to report crashes involving SAE Level 2 advanced driver assistance systems and Level 3–5 automated driving systems. Press release: https://www.nhtsa.gov/press-releases/nhtsa-orders-crash-reporting-vehicles-equipped-advanced-driver-assistance-systems
• NHTSA, A Framework for Automated Driving System Testable Cases and Scenarios, which describes scenario-based V&V approaches for ADS. URL: https://www.nhtsa.gov/document/framework-automated-driving-system-safety — exact publication year and document number should be treated as needs primary source validation.

The SGO is important because it creates a mandatory post-deployment V&V data stream that regulators can use to compare field performance against pre-deployment safety claims.

2.5 Cross-domain regulator guidance

Autonomous systems are not limited to road vehicles. The FDA’s AI/ML-based Software as a Medical Device action plan addresses lifecycle V&V for autonomous or semi-autonomous medical software:

• FDA, Artificial Intelligence/Machine Learning (AI/ML)-Based Software as a Medical Device (SaMD) Action Plan, 2021-01. URL: https://www.fda.gov/media/145022/download

NIST’s AI Risk Management Framework provides a general govern/map/measure/manage rubric:

• NIST, Artificial Intelligence Risk Management Framework (AI RMF 1.0), 2023-01. URL: https://www.nist.gov/itl/ai-risk-management-framework

2.6 SAE automation levels

The industry’s shared vocabulary for autonomy is SAE J3016. The 2021 revision is the current reference:

• SAE J3016_202104, Taxonomy and Definitions for Terms Related to Driving Automation Systems for On-Road Motor Vehicles, published 2021-04-30. URL: https://www.sae.org/standards/content/j3016_202104/

This source is load-bearing for any claim about what Level 2, Level 3, Level 4, and Level 5 mean. A company calling a supervised driver-assistance feature “Full Self-Driving” does not change the SAE level; the system is still Level 2 if the human driver remains responsible for the dynamic driving task.

V&V methods, the statistical mile problem, and a worked calculation

3.1 Evidence types

Modern ADS V&V combines at least four evidence types:

1. Simulation-based scenario testing — deterministic and stochastic scenarios injected into synthetic worlds. This is the only way to see rare and ethically unacceptable cases repeatedly.
2. Closed-course testing — physical tests with surrogate vehicles, pedestrians, and adversarial scenarios.
3. Public-road testing — real-world exposure, usually with safety drivers, collecting disengagements and crash data.
4. Formal and model-based verification — using requirements models, reachability analysis, and formal safety properties where tractable.

No single method is sufficient. Simulation can encode wrong assumptions; closed-course testing has limited scenario richness; public-road testing is too sparse for rare events.

3.2 Worked calculation: how many miles are needed?

A widely used logic, consistent with Koopman and Wagner’s discussion of validation miles, is the zero-failure confidence interval. Assume fatal crashes follow a Poisson process with rate \(\lambda\) per mile. If an AV fleet drives \(n\) miles with zero fatal crashes, the probability of observing zero events is:

\[

P(0 \text{ fatalities} \mid \lambda) = e^{-\lambda n}

\]

To be 90% confident that the true fatal crash rate is no greater than \(\lambda_0\), we set:

\[

e^{-\lambda_0 n} = 0.10

\]

Solving:

\[

n = \frac{-\ln(0.10)}{\lambda_0} = \frac{2.302585}{\lambda_0}

\]

Using NHTSA’s 2022 U.S. traffic fatality rate of approximately 1.35 fatalities per 100 million vehicle miles traveled:

\[

\lambda_0 = \frac{1.35}{100{,}000{,}000} = 1.35 \times 10^{-8} \text{ fatalities/mile}

\]

Then:

\[

n = \frac{2.302585}{1.35 \times 10^{-8}} = 170{,}561{,}851 \text{ miles}

\]

So a fleet would need approximately 171 million miles with zero fatal crashes to demonstrate, at 90% confidence, that its fatal crash rate is no worse than the 2022 U.S. human-driven baseline. At 95% confidence, the multiplier becomes \(-\ln(0.05) = 2.995732\):

\[

n = \frac{2.995732}{1.35 \times 10^{-8}} = 221{,}906{,}074 \text{ miles}

\]

That is approximately 222 million miles at 95% confidence.

If the target is a stricter superhuman rate of 1 fatality per 1 billion miles:

\[

\lambda_0 = 1 \times 10^{-9} \text{ fatalities/mile}

\]

Then:

• 90% confidence: \(n = 2.302585 / 10^{-9} = 2.30\) billion miles
• 95% confidence: \(n = 2.995732 / 10^{-9} = 3.00\) billion miles

Interpretation: To demonstrate superhuman fatal crash safety at 95% confidence using only public-road miles, the AV industry would need billions of miles with zero fatal events. That is why simulation, closed-course testing, scenario injection, and safety case logic are not optional; they are the only practical way to provide pre-deployment evidence for rare-event safety.

3.3 Parameter table

Company filings vs self-reported safety claims

Company SEC filings are not proof of safety, but they are the highest-quality source for what management itself discloses about risk, validation cost, and regulatory exposure.

4.1 Alphabet / Waymo

Alphabet’s Form 10-K includes risk factor language that Waymo and other “Other Bets” face significant competition and could incur substantial losses; it also identifies product risk, safety risk, and potential regulatory action. The company does not, in the 10-K, assert that its autonomous vehicle system is statistically safer than human drivers. We can say:

• Alphabet FY2023 Form 10-K, SEC EDGAR filing index: https://www.sec.gov/cgi-bin/browse-edgar?action=getcompany&CIK=0001652044&type=10-K

By contrast, Waymo’s own safety report and public safety data pages present self-reported safety metrics. Those are self-reported and are not equivalent to an independent regulator finding.

4.2 GM / Cruise

GM’s FY2023 Form 10-K risk factors state that autonomous vehicle technology may not be commercially viable, that safety incidents could damage reputation, and that regulatory approval is uncertain. Source:

• General Motors FY2023 Form 10-K, SEC EDGAR: https://www.sec.gov/cgi-bin/browse-edgar?action=getcompany&CIK=0001467858&type=10-K

4.3 Tesla

Tesla’s FY2023 Form 10-K states that its vehicles require active driver supervision and that regulatory authorities are increasingly scrutinizing advanced driver assistance systems. Tesla markets “Full Self-Driving capability” in customer-facing channels, but the regulatory and SAE definitions do not treat the system as autonomous in the Level 4/5 sense. Source:

• Tesla FY2023 Form 10-K, SEC EDGAR: https://www.sec.gov/cgi-bin/browse-edgar?action=getcompany&CIK=0001318605&type=10-K
• SAE J3016_202104, ibid.

This is the clearest marketing-vs-filing discrepancy: customer-facing language suggests autonomous capability, while the 10-K and SAE taxonomy require the human driver to remain engaged.

4.4 Aurora Innovation

Aurora describes its safety case framework and validation architecture in investor materials, but its 10-K similarly states that certification is uncertain and that the technology may fail to achieve commercial scale. Source:

• Aurora Innovation SEC filings, EDGAR: https://www.sec.gov/cgi-bin/browse-edgar?action=getcompany&CIK=0001828108&type=10-K

Patent evidence — required Tier-1 item

Granted patent evidence: I did not retrieve a verifiable USPTO/EPO/WIPO grant number in this offline session. I will not fabricate a patent number, title, or assignee.

To satisfy the hard patent requirement on a second pass, the correct search targets are:

• USPTO PatFT and Google Patents CPC classes: B60W60/00 (autonomous vehicle control), G05D1/021 (vehicle position/storage control for autonomous vehicles), G06F30/20 (simulation and V&V), and G07C5/00 (vehicle monitoring).
• Likely assignees: Waymo/Google, Aurora, GM Cruise, NVIDIA, Mobileye, Zoox/Amazon, and safety-tooling companies such as Foretellix or Edge Case Research.

This is an evidence gap in the note, not proof of absence.

Unit economics / business model

The safety certification and V&V stack monetizes in several ways. Every figure below is either cited from a filing or marked needs primary source validation.

6.1 Chip and safety-software vendors

NVIDIA sells the DRIVE compute platform and associated safety software to automakers and AV developers. The company self-reports that the platform targets ISO 26262 ASIL-D and supports redundant architecture and simulation. Source:

• NVIDIA autonomous vehicle safety page, self-reported: https://developer.nvidia.com/drive/safety

Mobileye sells EyeQ system-on-chip products and licenses a safety model known as Responsibility-Sensitive Safety, which imposes formal safety constraints on driving decisions. This is a per-chip/royalty model. Source:

• Mobileye Investor Relations, company self-description: https://ir.mobileye.com

Margins for automotive silicon are generally lower than for software, but exact AV-specific margins are not disclosed in the cited sources. needs primary source validation.

6.2 Simulation, V&V, and tooling vendors

Ansys and similar public simulation/engineering software firms sell subscription and perpetual licenses for safety analysis, closed-loop simulation, and functional safety workflows. The gross margin structure of large simulation software businesses is typically high, but the exact margin for AV V&V tools is not disaggregated in the citations. Source:

• Ansys autonomous vehicle safety analysis page: https://www.ansys.com/products/safety-analysis/autonomous-vehicle-safety

Monetization is recurring license/subscription revenue, and the value is captured by the tool vendor because V&V is a required cost before any vehicle can launch.

6.3 Certification and safety case services

UL Solutions sells safety certification, testing, and safety case evaluation services, including UL 4600. This is a project-based services model with fees tied to audit scope, duration, and product complexity. Margin data for UL 4600 services is not publicly broken out. needs primary source validation.

6.4 AV operators

Waymo, Cruise, Zoox, and Aurora are not primarily V&V vendors; they are buyers of V&V infrastructure. They monetize, or intend to monetize, ride-hailing, delivery, and trucking. For them, V&V is a cost center and a market-entry gate, not a profit line.

The value capture is asymmetric: safety tooling and certification providers collect revenue regardless of whether an AV program succeeds; AV operators only realize value after passing certification and achieving commercial deployment.

Disconfirming evidence

The thesis that formal safety certification and V&V are necessary and material for autonomous systems would be weakened if:

1. An independently audited, large-scale deployment shows an autonomous system with no ISO 26262/SOTIF/UL 4600 safety case and no statistical validation, yet real-world severe crash rates are multiple times safer than the human baseline and remain so across millions of miles.
2. Regulators accept self-reported safety metrics without independent crash-reporting, scenario testing, or safety case review, making certification a paper exercise with no predictive value.
3. A major certified system passes ISO 26262 ASIL-D and UL 4600 but still exhibits repeated systematic hazards from machine learning misperception, proving the standards do not capture the dominant risk.
4. Company filings drop autonomous-vehicle safety and certification from their risk factors, and no NHTSA crash-reporting enforcement or FDA AI/ML SaMD oversight remains.
5. The missing granted-patent evidence is never retrievable, and later investigation shows no assignee holds issued claims on safety case automation, scenario-based V&V, or redundancy architecture; that would weaken the “moat” interpretation of the certification stack.