April 17, 2018
To ensure the rising number of electronic functions being introduced with automated driving remain functionally safe, OEMs need electronic control unit (ECU) software that is developed and integrated in compliance with the ISO 26262 functional safety standard.
This requires safety measures to be implemented and safety analysis to be performed. What the standard requires in detail, and how great the impact on the development is, depends on the Automotive Safety Integrity Level (ASIL). Choosing the right level is a balancing act; classifying vehicle functionality with an ASIL that is too high will generate unnecessary costs, but going too low will not decrease safety risks to a reasonable level.
In this free 60-minute webinar, Steffen Kuhn, Consulting Manager at Elektrobit, will discuss the derivation of ASIL, as a key aspect that must be considered at the beginning of any new development.
Download the slides:
- How much safety is necessary - derivation of the ISO 26262 Automotive Safety Integrity Level (ASIL) by Steffen Kuhn, Consulting Manager, Elektrobit
View the webinar recording: