Homologation, Regulations & Liability
10 chapters 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.
How You Learn
Video and text stay in sync. As you scroll through the chapter, the video jumps to the matching explanation automatically.
Learning Objectives
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.
Chapters
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Diagrams & Visuals
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
ALKS Approval Evidence Matrix
Master Homologation, Regulations and Liability for Modern Vehicles
Work through type approval, the key UN Regulations, the ISO 26262 bridge and product liability to build one body of evidence that serves the assessor, the authority and, someday, a court.
Start Learning Now