EV type approval, ASIL decomposition and CSMS: answered in 3 seconds for OEM compliance engineers.

UNECE Regulation No. 100 (R100) governs the type approval of Battery Electric Vehicles (BEVs) and their rechargeable energy storage systems (REESS). Rev 3 (effective June 2021) introduced significant additional requirements: Part I covers the vehicle type approval including electrical safety requirements during charging, crash protection (post-crash electrical safety test simulating 50 km/h frontal barrier plus pole test), and protection against electrical hazards during normal operation (IP67 minimum for high-voltage components). Part II governs REESS-specific type approval: protection against overcharge, over-discharge, over-temperature; thermal runaway notification requirement (the REESS must provide a warning to the driver at least 5 minutes before a thermal event posing danger to occupants); vibration test to simulate operational road loads; thermal shock and cycling. R100 Rev 3 explicitly requires a Battery Management System (BMS) functional description and requires that the BMS cutoff functions are validated. Compliance requires submission of a technical file to the type approval authority (e.g., TRL in UK, DREAL in France) and testing at an accredited technical service.

ISO 26262:2018 (Road vehicles — Functional Safety) governs the development of safety-related electrical and electronic (E/E) systems in passenger vehicles. For EV Battery Management Systems (BMS), the safety analysis typically identifies hazardous events requiring ASIL D (highest) or ASIL C assignment — for example, uncontrolled energy release causing fire, or loss of BMS control during high-speed driving. ASIL decomposition (ISO 26262 Part 9, cl.5.4) allows the assigned ASIL D to be decomposed into two independent safety requirements each carrying ASIL B(D) — meaning the BMS hardware and the BMS software can each be developed to ASIL B independently, provided the channels are sufficiently independent (ISO 26262 Part 9 criteria for independence). Part 6 (Software level) specifically requires: ASIL B software to use formal or semi-formal notation for software architecture, with structural coverage metrics MC/DC for unit testing; ASIL D prohibits certain modelling notations and requires stricter independence of safety analysis from design. For OEM supply chain compliance, Tier 1 BMS suppliers must provide a Part 8 (Supporting processes) compliant development interface agreement and a safety case with ASIL decomposition documentation.

UNECE Regulation No. 155 (R155) requires vehicle manufacturers to implement and maintain a certified Cybersecurity Management System (CSMS) covering the entire vehicle development lifecycle. R155 is mandatory for new vehicle type approvals in EU and UN contracting parties from July 2022, and for all new vehicles of approved types from July 2024. Key requirements: (1) CSMS certification — OEM must obtain CSMS certification from a national type approval authority (e.g., KBA in Germany, DREAL in France) demonstrating that cybersecurity processes are implemented across design, development, production, post-production and decommissioning. (2) Vehicle type approval — each vehicle type must receive a VTA (Vehicle Type Approval) for cybersecurity demonstrating that vehicle-specific threat analysis and risk assessment (TARA) has been completed per ISO/SAE 21434, identified risks are mitigated, and monitoring processes for in-field cybersecurity incidents are in place. (3) OTA software updates — Regulation No. 156 (Software Updates, SUMS) governs OTA update type approval. OEMs must demonstrate that software update packages are authenticated, integrity-protected, and that the vehicle cannot be placed in a hazardous state by an update. R155 Annex 5 provides the list of cybersecurity threats that must be addressed in the TARA.

Regulation (EU) 2019/631 (revised by Regulation 2023/851) sets CO2 fleet average targets for passenger cars and light commercial vehicles. For passenger cars: 2025 target — 15% reduction from the 2021 baseline (approximately 93.6 gCO2/km WLTP fleet average for the EU fleet). From 2030 — 55% reduction from 2021 baseline (approximately 49.5 gCO2/km). From 2035 — 100% reduction (zero emissions only). Penalty mechanism: for each g/km above the target, the OEM pays €95 per vehicle sold in that model year. For a manufacturer selling 500,000 vehicles with an average 3 g/km above target, the penalty exceeds €142.5 million per year. The penalty applies per manufacturer or per pool (manufacturers can pool to average their fleet CO2 across the pool). From 2025, the super-credit mechanism for ZEVs and LEVs is phased out. Manufacturers must report fleet CO2 data annually; the European Commission calculates the final specific emission target per manufacturer based on the mass-based target curve and sales-weighted average vehicle mass.

Euro NCAP’s 2026 protocol (announced 2024, applying to vehicles tested from 2026) introduces several EV and advanced safety-specific updates. Key changes: (1) Battery protection in side pole impact — the Mobile Progressive Deformable Barrier (MPDB) side test is supplemented with a pole impact test specifically designed to assess lateral battery intrusion in BEV architectures; battery integrity after impact is evaluated (post-crash leakage, thermal event indicators). (2) Far-side occupant protection — expanded mandatory testing of occupant kinematics when the struck-side occupant migrates across the vehicle centre — relevant for bench-seat configurations increasingly used in BEVs. (3) Vulnerable road user (VRU) detection at junction — new scenarios assessing AEB performance at intersections for cyclists and pedestrians approaching from the side, where BEV silent operation creates increased risk. (4) Driver monitoring system (DMS) — systems that detect driver inattention or impairment are now rated and contribute to the safety assist score. (5) Lane support improvements — evaluation of lane departure correction authority and response in highway conditions with degraded lane markings. Scores from 2026 tests are not directly comparable to pre-2026 scores.

Whole Vehicle Type Approval (WVTA) under EU Regulation 2018/858 (replacing Directive 2007/46/EC) is required for every new vehicle type placed on the EU market. The WVTA process for a new EV involves: (1) Pre-approval phase — OEM submits a preliminary information document to the type approval authority (TAA); TAA and OEM agree on the applicable UN Regulations (typically 40-60 regulations for a full BEV including R100, R10, R48, R155, R156, R13-H, etc.); (2) Type approval testing phase — contracted technical services (TS, accredited test laboratories) conduct tests for each applicable regulation and issue test reports (typically 18-30 months for a clean-sheet vehicle); (3) Certificate of Conformity (CoC) data preparation — OEM compiles all test reports, Declaration of Conformity and technical file; (4) WVTA issuance — TAA reviews and issues EU-wide type approval certificate (EU-wide recognition under Mutual Recognition); (5) Conformity of Production (CoP) — ongoing production audits by TAA or approved body to verify that series production vehicles conform to the approved type. Total WVTA timeline: 24-36 months from design freeze to market launch for a new vehicle architecture.