Functional Safety Certification for Last-Mile Delivery Robots: ISO 26262-6 Explained

Date
2027-01-06
Location
Online
Host
Zach L

About this event

A Tabletop Exercise for Safety Engineers pursuing functional safety certification. A live 30-minute tabletop exercise on ISO 26262-6 (Automotive Software Development) for last-mile delivery robots, built for safety engineers pursuing functional safety certification. What We'll Cover: What ISO 26262-6 (Automotive Software Development) requires and how its scope applies to last-mile delivery robots Mapping ISO 26262-6 clauses to the certification evidence assessors expect System-specific hazards and safety functions typical of last-mile delivery robots Common findings that delay certification, and how to avoid them A practical readiness roadmap for safety engineers preparing for assessment Related topics: ISO 26262-6 · Last-Mile Delivery Robots · functional safety certification · functional safety assessment · Tabletop Exercise · Safety Engineers · safety lifecycle · compliance evidence · SIL · PL · risk assessment · safety case Critical Systems Analysis provides embedded functional safety consulting for ISO 26262-6. Learn more: https://criticalsystemsanalysis.com Partner with us: https://meetings.hubspot.com/benjamin-twombly/strategic-partnerships

Topics

Registration

View event page

About ISO 26262-6 (Automotive Software Development)

This event covers the compliance, engineering, and verification requirements defined by ISO 26262-6.

Part 6 of ISO 26262 specifies the software development lifecycle for automotive safety-related software: architecture, unit design and implementation, verification at each level, and integration testing, with methods graded by ASIL.

What it regulates

Software safety requirements, architectural design principles (freedom from interference, partitioning), coding guidelines, unit verification incl. structural coverage targets, and software integration and embedded testing.

Who must comply

Automotive software teams from AUTOSAR platform suppliers to application developers and their verification organizations.

Key requirements of ISO 26262-6

  • Software safety requirements specification and verification
  • Architectural design: hierarchy, restricted size/complexity, ASIL-oriented partitioning
  • Unit implementation and verification with coverage metrics (statement/branch/MC/DC by ASIL)
  • Integration verification and verification of embedded software
  • Method tables per ASIL

Key concepts: ISO 26262-6

QM
Quality-managed (no ASIL) software still coexisting with safety software under partitioning arguments.
Freedom from interference
Evidence that lower-ASIL or QM software cannot corrupt higher-ASIL functions (memory, timing, communication).
MC/DC
Modified condition/decision coverage — the structural coverage bar associated with ASIL D unit verification.
Model-based development
Common automotive practice with code generation, shifting verification to models plus generated-code assurance.

Frequently asked questions: ISO 26262-6

Can open-source software run at ASIL B or higher?

Only through qualification routes of Part 8 (safety element out of context, proven-in-use, or qualification of software components) plus partitioning; practical systems isolate open-source in QM partitions with monitored interfaces.

Is MISRA C mandatory?

Part 6 requires suitable coding guidelines; MISRA C is the de facto choice for C, enforced with static analysis and documented deviations — auditors expect it or an equivalent justified subset.

Standard information based on the published text of ISO 26262-6 (Automotive Software Development). Event content is provided by the host. For authoritative guidance, consult the official standard body.