Homologation, Regulations & Liability
Type approval and UN R79, R13-H, R157, R155/R156 explained for safety engineers: how ISO 26262 evidence enters the approval file, what state of the art means in court, and who is liable when the system drives instead of the human.
- Chapters
- 12
- Chapters
- Key UN Regulations
- 5
- Key UN Regulations
- ALKS Assessment Pillars
- 5
- ALKS Assessment Pillars
- Liability Channels
- 3
- Liability Channels
- 01Two Compliance Worlds
- 02Type Approval 101
- 03The Regulatory Map
- 04UN R79: Steering, ACSF & the Level 2 Fence
- 05UN R13-H & the CEL Annexes
Why it pays for itself
Connect two compliance worlds
ISO 26262 conformance and type approval are different obligations with different judges. Learn how the safety case you already build becomes evidence in the regulatory approval file - and where the gaps are.
Navigate the key UN regulations
Get working knowledge of R79 for steering and lane keeping, R13-H for braking, R157 for Level 3 ALKS, and R155/R156 for cybersecurity and software update management - the regulations that gate modern E/E functions.
Understand liability when the system drives
See what "state of the art" means in a courtroom, how product liability channels work, and why an approved automated system shifts responsibility onto the manufacturer while it is driving.
What you’ll be able to do
Read a UN regulation like a safety concept
Recognize the warning cascades, authority limits and safe states that R79, R13-H and R157 pre-decide for your functional safety concept.
Feed ISO 26262 evidence into the approval file
Map item definitions, safety concepts, FMEA/FTA and verification results into CEL and R157 assessment packages that survive a technical service review.
Design to prescribed safe states and timings
Build degradation and warning strategies that satisfy the transition-demand and minimum-risk-maneuver requirements written into law.
Manage RXSWIN and OTA change impact
Decide when a software update touches approval-relevant behavior and triggers an extension rather than a silent rollout.
Build a defensible state-of-the-art argument
Inventory the yardsticks, justify deviations and date-stamp decisions so compliance reads as due care in court, not after the fact.
Run the post-SOP field loop
Wire field data, DSSAD occurrences and in-service reporting back into HARA, updates and the approval to close the lifecycle loop.
Chapter by chapter
- 01
Two Compliance Worlds
Why the legal world of type approval and the engineering world of ISO 26262 answer different questions, and why passing one never guarantees the other.
- "Approved" means minimum conformity at one point in time, not safe
- "ISO 26262 compliant" is strong due-care evidence, not a liability shield
- The two worlds interlock more every year, R157 most of all
- 02
Type Approval 101
How type approval actually works: the 1958 and 1998 Agreements, the EU whole-vehicle framework, US self-certification, and what an approval file really contains.
- E-marks, GTRs, and the FMVSS self-certification contrast
- Approval authority, technical service, manufacturer, suppliers
- Component, STU, system and whole-vehicle approval levels
- 03
The Regulatory Map
A guided map of the safety-relevant regulations for E/E systems and how the pieces stack from steering and braking up to Level 3 automation.
- Which regulation governs which function
- How the EU General Safety Regulation pulls them together
- Where complex-electronics evidence is demanded
- 04
UN R79: Steering, ACSF & the Level 2 Fence
From the ban on autonomous steering to the ACSF category system, the hands-off warning cascade and the driver-commanded lane change, and how R171 DCAS opens the gate.
- ACSF categories A-E, and why B2, D and E stayed empty
- The B1 cascade: optical at 15 s, acoustic at 30 s, then disengage
- Category C lane change: arm, command, check, execute, resume
- 05
UN R13-H & the CEL Annexes
Classic prescriptive braking plus the complex-electronics annexes where safety documentation first became a type-approval requirement, decades before R157 made it famous.
- Dual-circuit residual performance and prescribed telltales
- CEL asks for the safety concept, FMEA/FTA and fault reaction
- The assessment day: document review, walkthrough, fault-injection demo
- 06
UN R157: ALKS, the First Level 3 Regulation
The first binding regulation for a system that drives instead of the human, blending prescriptive tests, simulation and an audited safety case as a condition of market access.
- State machine: transition demand, minimum risk maneuver, emergency maneuver
- The competent-and-careful-driver benchmark across cut-in and cut-out
- The five-pillar NATM assessment, DSSAD, and the first real approvals
- 07
UN R155 & R156: Cybersecurity & Software Updates
The two-layer model that made a certified management system a condition of selling cars and turned over-the-air updates into a regulated, RXSWIN-tracked activity.
- CSMS and SUMS management systems plus per-type approvals
- RXSWIN: when an update forces an approval extension
- ISO/SAE 21434 and ISO 24089 as the engineering backbone
- 08
The ISO 26262 Bridge
What the standard and the regulations each contribute, where they differ, and how to run the mapping between them on a real project.
- Voluntary and risk-based versus law and prescriptive
- ISO 26262 gives structured evidence; regulations give hard requirements
- The gaps only one side owns, and the ones they share via SOTIF
- 09
State of the Art & Product Liability
The three-tier state-of-the-art doctrine and the liability channels for software-defined vehicles, including the reshaped EU Product Liability Directive and the Level 3 responsibility shift.
- Rules of technology, state of the art, state of science and technology
- Strict liability, negligence and traffic-law owner liability
- New PLD: software as product, disclosure duties, the Level 3 shift
- 10
One Evidence Backbone, Pitfalls & Outlook
Building a single body of evidence that serves the assessor, the technical service and, someday, a court, plus the classic traps and where regulation is heading.
- One baseline, two certificates: homologation as a thread, not a phase
- Marketing that outruns the ODD, and updates that outrun the paperwork
- The post-SOP field loop and the practitioner checklist
Not just text: the visual toolkit
Two Compliance Worlds Map
Lays the legal world of approvals and courts alongside the engineering world of safety cases to show where they meet and diverge.
B1 Hands-Off Warning Escalation
Times the R79 category B1 cascade from hands-off through the optical and acoustic warnings to prescribed disengagement.
ALKS Operating State Machine
Maps the R157 flow between ALKS active, transition demand, minimum risk maneuver and emergency maneuver with their legal timings.
Minimum Risk Maneuver to Standstill
Traces the ALKS safe state that stops the vehicle with hazard lights when the driver does not resume control.
Dual-Circuit Braking Residual
Shows how a single failure in the braking transmission still leaves the prescribed R13-H secondary performance.
CEL Fault-Injection Reaction Chain
Follows a witnessed fault from injected sensor or bus failure through detection to the documented reaction and driver warning.
Approving a Level 3 Highway Pilot Against R157, R79 and R155/R156
A motorway ALKS in the style of Mercedes DRIVE PILOT seeks type approval: a 60 km/h conditional-automation system where the driver may legally disengage. The example walks the evidence trail from the R79 lane-keeping base and the R157 state machine through the audited safety case to the manufacturer accepting liability while the system drives.
- R79 category B1 lane keeping documented as the base function with lateral limits and the hands-off cascade
- R157 state machine implemented: transition demand with ~10 s lead, minimum risk maneuver to standstill, emergency maneuver bounds
- Competent-and-careful-driver benchmark evidenced across cut-in, cut-out and lead-vehicle braking scenarios
- Annex 4 safety case assembled from ISO 26262, ISO 21448 SOTIF and ISO/SAE 21434 work products
- R155 CSMS and R156 SUMS approvals stacked underneath, with the RXSWIN baseline frozen to the safety case
- DSSAD occurrence logging wired in, and the manufacturer accepting responsibility for accidents in-ODD
Unlock the full evidence matrix mapping every regulatory clause to its ISO 26262 work product
Who this guide is for
- Safety engineers whose work products end up in a type approval file
- Homologation and regulatory affairs engineers bridging to the ISO 26262 team
- Engineering managers planning L2/L3 features across UN regulation boundaries
- Anyone asking who is legally responsible when an automated system causes harm
Frequently Asked Questions
Common questions about Homologation, Regulations & Liability
Start the course today
A free account unlocks one full concept guide, 3 work product templates, 1 guided process, the Markov simulator, and 5 practice exams per month. The Pro and Expert plans unlock more of the 77-guide library. No credit card required.