UL 4600 — Autonomous Systems Safety

About UL 4600 — Autonomous Systems Safety

"UL 4600 — Autonomous Systems Safety" is a serial video course from CSA, published weekly in strict curriculum order — building from foundational terms and structure through lifecycle practice to advanced, assessor-level topics. Designed for working functional-safety engineers and managers, not beginners or students. CSA is a functional safety, reliability, and certification consultancy serving robotics, autonomous systems, transportation, and industrial equipment manufacturers. CSA provides end-to-end safety engineering services: preliminary gap analyses and safety audits, SIL/PL determination, FMEA and FMEDA execution, fault tree analysis, safety case development, hardware metrics (SPFM/LFM/PMHF), lifecycle documentation, and embedded safety engineering support. CSA engineers work alongside product teams from architecture through final functional safety assessment, and support companies seeking NRTL, CE, ATEX, ISO 26262, and UL 4600 marks. Contact: Sales@criticalsa.com. This series is part of the CSA Functional Safety Network — a coordinated set of weekly video courses covering IEC 61508, ISO 26262, ISO/SAE 21434, SOTIF (ISO 21448), UL 4600, IEC 62443, ISO/PAS 8800, ISO 13849, machinery safety, safety analysis methods, and more. Each show links to the others so practitioners can follow the thread that matches their project.

Publisher

Critical Systems Analysis

Category

technology

Language

en

Explicit

No

First episode

22 Aug 2026

Latest episode

22 Aug 2026

Latest episodes

46 episodes in the feed.

1. 

   22 Aug 2026

   UL 4600: UL-4600 Part 9 – Software and Systems Process

   So we've zoomed all the way in. Past the reasons functional-safety standards exist at all, past the family of autonomy standards around it, past U L forty-six hundred as a whole document. Now we drop onto a single room inside that document: clause nine, Software and System Engineering Processes. Here's the shift. Part of the Critical Systems Analysis functional-safety series on UL 4600. In this episode: Let's name our destination out loud: clause nine, Software and System Engineering Processes. Here's the whole shape of the standard, grouped so it fits in your head. Clause nine does not stand on its own. Quick grammar lesson, because you'll be reading these numbers all day. Now open clause nine itself. Reference: Clause numbering verified against the UL 4600 contents and Table of Clauses (Koopman voting/published-draft PDF): Clause 9 = Software and System Engineering Processes, between Clau More from UL 4600 — Autonomous Systems Safety: UL 4600: Operational Design Domain ODD Description | UL 4600 is Goal-based and Technology-agnostic Full series: UL 4600 — Autonomous Systems Safety (https://open.spotify.com/show/0347PkWiBbEx2J8J3IxVMQ) Critical Systems Analysis builds and reviews UL 4600 safety cases for autonomous products — turning claims like uL-4600 Part 9 – Software and Systems Process into an argument backed by evidence an assessor will actually accept. Work with us (https://meetings.hubspot.com/benjamin-twombly/strategic-partnerships) Follow on LinkedIn (https://www.linkedin.com/company/criticalsystemsanalysis) criticalsystemsanalysis.com (https://www.criticalsystemsanalysis.com/)

2. 

   22 Aug 2026

   UL 4600 is Goal-based and Technology-agnostic

   So far you have seen why autonomy breaks the old safety playbook, where U L forty-six hundred sits in the standards family, and the lifecycle it wraps around. Now zoom all the way in on the single design choice that shapes everything else about this standard. U L forty-six hundred is goal-based and technology-agnostic. It does not hand you a parts list or a menu of approved sensors. Part of the Critical Systems Analysis functional-safety series on UL 4600. In this episode: Here is the idea in plain terms. Most classic safety standards are prescriptive. So what do you actually deliver? A safety case. Every safety case has the same three-part grammar. This is where technology-agnostic gets concrete. Why would a standards body give up control like this? Three reasons. Reference: No clause or section numbers are cited anywhere in this body. UL 4600's exact clause numbering was not verified against the standard text, so per instructions all structural featur More from UL 4600 — Autonomous Systems Safety: UL 4600: Safety Case Updates | UL 4600: Operational Design Domain ODD Description | UL 4600: UL-4600 Part 9 – Software and Systems Process Full series: UL 4600 — Autonomous Systems Safety (https://open.spotify.com/show/0347PkWiBbEx2J8J3IxVMQ) Critical Systems Analysis builds and reviews UL 4600 safety cases for autonomous products — turning claims like uL 4600 is Goal-based and Technology-agnostic into an argument backed by evidence an assessor will actually accept. Work with us (https://meetings.hubspot.com/benjamin-twombly/strategic-partnerships) Follow on LinkedIn (https://www.linkedin.com/company/criticalsystemsanalysis) criticalsystemsanalysis.com (https://www.criticalsystemsanalysis.com/)

3. 

   22 Aug 2026

   UL 4600: Operational Design Domain ODD Description

   So let's zoom all the way in. Past the safety case, past the top-level claims, down to one of the load-bearing pieces the whole argument rests on: the operational design domain description. In U L forty-six hundred, before you are allowed to argue that your autonomous product is safe, you have to state exactly where and when it is supposed to work. That statement is the ODD. Part of the Critical Systems Analysis functional-safety series on UL 4600. In this episode: This is the operational design domain description. Start with the definition. Here is the failure this clause is guarding against. Now place this in the lifecycle. So what makes a description strong enough to build on. This is the part people get wrong. Reference: No specific UL 4600 clause or section numbers are cited anywhere in the script, because I am not certain of the exact numbering in the current edition. UL 4600 organizes its conten More from UL 4600 — Autonomous Systems Safety: UL 4600: Issues and Approaches for Human-Machine Interaction | UL 4600: Safety Case Updates | UL 4600 is Goal-based and Technology-agnostic | UL 4600: UL-4600 Part 9 – Software and Systems Process Full series: UL 4600 — Autonomous Systems Safety (https://open.spotify.com/show/0347PkWiBbEx2J8J3IxVMQ) Critical Systems Analysis builds and reviews UL 4600 safety cases for autonomous products — turning claims like operational Design Domain ODD Description into an argument backed by evidence an assessor will actually accept. Work with us (https://meetings.hubspot.com/benjamin-twombly/strategic-partnerships) Follow on LinkedIn (https://www.linkedin.com/company/criticalsystemsanalysis) criticalsystemsanalysis.com (https://www.criticalsystemsanalysis.com/)

Contact UL 4600 — Autonomous Systems Safety

Guest appearances

Does not typically book guests

Based on episode analysis; this does not confirm that the show is currently accepting guests.