Generated by GPT-5-mini| Automotive Safety Integrity Level | |
|---|---|
| Name | Automotive Safety Integrity Level |
| Abbreviation | ASIL |
| Standard | ISO 26262 |
| Domain | Automotive safety |
| Established | 2011 (second edition 2018) |
Automotive Safety Integrity Level
Automotive Safety Integrity Level is a risk classification scheme used in the ISO 26262 standard to specify automotive functional safety requirements for electrical and electronic systems in passenger vehicles. It guides manufacturers such as Volkswagen, Toyota, Ford Motor Company, General Motors, Honda and suppliers like Bosch, Continental AG, Denso, Magna International to derive safety goals, design measures, and verification plans through a structured hazard analysis and risk assessment. ASIL influences system architecture, software development, hardware design, and tool qualification for companies including Nissan, BMW, Mercedes-Benz, Hyundai Motor Company, Stellantis, Renault, Tesla, Inc., Aptiv, ZF Friedrichshafen AG, and Valeo.
ASIL provides four classification levels—A, B, C, D—used to express required rigor for automotive safety functions, with D imposing the highest rigor and A the lowest, similar in intent to integrity levels in IEC 61508. ASIL determination considers severity, exposure, and controllability factors derived from operational scenarios like those encountered by Autonomous vehicle programs at Waymo, Cruise (company), and research institutions such as Massachusetts Institute of Technology, Stanford University, Technical University of Munich, Karlsruhe Institute of Technology. Regulatory and industry stakeholders—European Commission, NHTSA, UNECE, SAE International, IEEE—influence ASIL interpretation and deployment across ecosystems involving OEMs, tier-1 suppliers, and semiconductor vendors like Intel, NVIDIA, Qualcomm, Infineon Technologies, NXP Semiconductors.
The ASIL determination process begins with hazard analysis and risk assessment (HARA), conducted by cross-functional teams from departments such as SAE International committees, OEM safety offices at Toyota Research Institute, Volkswagen Group Research, and safety labs at TÜV Rheinland, DEKRA, SP Technical Research Institute of Sweden. HARA evaluates hazardous events by mapping driving situations studied by programs like Euro NCAP, IIHS, JNCAP, ANCAP, and research projects funded by Horizon Europe, ARPA-E. The process uses contribution matrices and severities informed by incidents such as those analyzed by National Transportation Safety Board, Transport Canada, Federal Highway Administration, and statistical analyses from Insurance Institute for Highway Safety. Inputs from standards bodies—ISO, IEC, SAE International—and legal frameworks like UNECE WP.29 shape the assignment of ASIL levels.
From ASIL classification, safety goals are derived and refined into technical safety requirements, architectural constraints, and verification criteria adopted by OEMs including Toyota, Ford, Mercedes-Benz Group, Volvo Cars. Safety goals relate to functions such as Advanced Driver-Assistance Systems, Electronic Stability Control, Airbag deployment, Brake-by-wire, Steering-by-wire, and battery management systems produced by suppliers like LG Chem, Samsung SDI, CATL. Derived requirements reference models and methods promoted by ISO 26262 working groups, formal methods research at INRIA, CMU, ETH Zurich, model-based design from MathWorks, and software engineering practices from MISRA, AUTOSAR associations.
The functional safety lifecycle defined in ISO 26262 guides phases from concept through decommissioning, practiced by development organizations at Bosch, Continental, Aptiv, and research consortia at CARNET, IVI. Lifecycle activities include concept phase HARA, system design, hardware-software integration, production release, operation, and service actions overseen by compliance teams and notified bodies such as TÜV SÜD, SGS, Bureau Veritas. The lifecycle aligns with product development models used by Siemens Digital Industries, IBM, Accenture, and Capgemini for safety management, change control, and configuration management in platforms developed by ARM Holdings, Cadence Design Systems, Synopsys.
Implementing ASIL requirements involves hardware measures (redundancy, diagnostics), software measures (MISRA C, static analysis), and verification tools from vendors like MathWorks, Vector Informatik, Rational Software (IBM Rational), LDRA, Coverity by Synopsys, Polyspace by MathWorks, and model checkers developed in academia at University of Oxford, University of Cambridge, University of California, Berkeley. Suppliers integrate safety mechanisms in microcontrollers from Renesas Electronics, Microchip Technology and SoCs from NVIDIA, Intel with safety-oriented operating systems and hypervisors from Green Hills Software, Wind River Systems. Tool qualification and tool confidence levels follow ISO 26262 guidance and are audited by certification bodies such as TÜV Rheinland and DEKRA.
Assessment and certification activities are executed by accredited assessors and notified bodies including TÜV SÜD, DEKRA, SGS, Bureau Veritas to demonstrate conformance to functional safety claims for vehicles regulated by agencies like NHTSA, UNECE, European Commission. Compliance strategies involve independent verification, validation testing at facilities such as HORIBA MIRA, Millbrook Proving Ground, and cybersecurity alignment with ISO/SAE 21434 coordinated with industry alliances like GENIVI Alliance and AUTOSAR. Litigation and recall analyses by NTSB, Transport Canada and research by RAND Corporation and IIHS inform continuous improvement of ASIL application across manufacturers and suppliers.
Category:Automotive safety