Homologation & Regulations
Learn how ISO 26262 work meets type approval: the UNECE system, the regulations that gate E/E functions, how safety evidence enters an approval file, and what state of the art and product liability mean for engineers.
- Chapters
- 12
- Chapters
- UN regulations in depth
- 5
- UN regulations in depth
Quick answers
- What is homologation in ISO 26262 terms?
- Homologation, or type approval, is the legal process by which an authority certifies that a vehicle type meets the applicable regulations (in most of the world the UN regulations developed at UNECE WP.29) before it may be sold or registered. ISO 26262 is an industry standard, not a law: conforming to it does not make a vehicle street-legal, and holding type approval does not prove functional safety or shield against liability. The two interlock instead: regulations such as UN R157 explicitly audit the manufacturer's safety processes and safety case, which is where the ISO 26262 work products become regulatory evidence.
- What is UN Regulation No. 157 (ALKS)?
- UN R157 is the first international regulation approving a Level 3 automated driving function: the Automated Lane Keeping System, initially limited to motorway use at up to 60 km/h, where the driver may legally disengage from the driving task. It prescribes a state machine with a transition demand giving the driver roughly 10 seconds of lead time, a minimum risk maneuver to standstill if the driver does not respond, bounds on emergency maneuvers, a competent-and-careful-driver performance benchmark for scenarios like cut-in and lead-vehicle braking, DSSAD data recording of occurrences, and an Annex 4 audit of the manufacturer's safety management system and safety case.
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
Separate safe from legal
Explain what ISO 26262 conformance and type approval each establish, and what neither does.
Navigate the key UN regulations
Know what R79, R13-H, R157, R155 and R156 require of E/E functions.
Feed the approval file
Map safety work products to the evidence regulators assess.
Argue state of the art
Build an argument about the state of the art that holds up under scrutiny.
Understand liability exposure
See how liability channels and the Level 3 shift affect the safety file.
Chapter by chapter
- 01
Two Compliance Worlds
Separate safe from legal, get the vocabulary straight, drop common misconceptions, and see why the topic grew after 2020.
- Safe versus legal
- Vocabulary
- Misconceptions
- 02
Type Approval 101
Learn how UNECE rules are made, how type approval differs from self-certification, and how an approval proceeds in the EU frame.
- The UNECE rulebook
- Approval versus self-certification
- Approval step by step
- 03
The Regulatory Map
Identify vehicle categories, the regulations that matter for E/E safety, and the EU General Safety Regulation wave.
- Vehicle categories
- Key regulations
- General Safety Regulation
- 04
UN R79: Steering, ACSF and the Level 2 Fence
Follow R79 from its category system through hands-off warnings and assisted lane changes, and see how UN R171 opens the gate.
- ACSF categories
- Hands-off warnings
- UN R171
- 05
UN R13-H, Braking and the CEL Annexes
See how braking is regulated and how the complex electronic system annexes assess the safety concept behind the hardware.
- Prescriptive braking rules
- CEL annexes
- CEL assessment
- 06
UN R157: ALKS, the First Level 3 Regulation
Work through the ALKS operating logic, driver availability and data recording, the performance benchmark and the multi-pillar approval.
- Operating logic
- DSSAD
- Multi-pillar assessment
- 07
UN R155 & R156: Cybersecurity and Software Updates
Understand the two-layer model of management system and type approval, the RXSWIN, and the interplay with safety.
- Two-layer model
- RXSWIN
- Safety interplay
- 08
The ISO 26262 Bridge
Map ISO 26262 work products to regulatory evidence, add SOTIF where regulations need it, and do the mapping on a project.
- Compliance stack
- SOTIF in the stack
- Project mapping
- 09
State of the Art Argumentation
Learn what state of the art means legally, how ISO 26262 serves as codified practice, and how to argue at the frontier.
- Three-tier ladder
- Codified practice
- Arguing at the frontier
- 10
Product Liability for Software-Defined Vehicles
Follow the liability channels, the defect categories in engineering terms, the 2024 EU reform and the Level 3 responsibility shift.
- Liability channels
- Defect categories
- EU 2024 reform
- 11
One Evidence Backbone, Three Audiences
Write evidence once for safety assessors, regulators and courts, and see where homologation hooks into the lifecycle and the supply chain.
- Three readers
- Lifecycle hooks
- Field loop
- 12
Pitfalls, Marketing Traps and What Comes Next
Avoid the pitfalls that keep repeating, use a practitioner checklist, and see where the regulatory frontier is moving.
- Recurring pitfalls
- Practitioner checklist
- Where it is moving
Read all 12 chapters with Expert.
Start with a free account: the complete Functional Safety Concept guide and 5 practice exams a month, then upgrade when you need this guide.
Expert plan pricingWho 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
Start the course today
A free account unlocks one full concept guide, 3 work product templates, 1 guided process, the Markov and RBD simulators, and 5 practice exams per month. The Pro and Expert plans unlock more of the 93-guide library. No credit card required.
Continue with
Where this topic leads next.
- Verification and assessmentProduction, Operation, Service & DecommissioningISO 26262-7 governs the safety lifecycle after design release: production controls, operation and service instructions, field monitoring, repair and diagnostics, and safe end-of-life decommissioning of high-voltage and pyrotechnic systems.
- Vehicle domainsActuator SafetyMotors, valves and relays are where safety goals become physical: learn how actuation channels fail stuck or runaway, how feedback and diagnostics catch it, and how safe states from de-energize to active hold are engineered and quantified.
- Verification and assessmentVerification & ValidationLearn multi-level verification from unit testing through system and vehicle validation with ASIL-dependent coverage criteria. Covers reviews, HIL/SIL testing, fault injection, MC/DC coverage, and evidence management.