ÁùºÏ²ÊÖ±²¥¿ª½±

How is ISO 26262 Evolving?

In 2018, ISO 26262 underwent a major update and added two new standards: requirements for semiconductors and for motorcycles, trucks, and buses. Guidance was added on model based development, software safety analysis, dependent failure analysis, fault tolerance, and more. 

ISO 26262¡¯s Automotive Safety Integrity Levels (ASILs) are based on three variables: severity, probability of exposure, and controllability by the driver. Since ISO 26262 assumes that someone is driving the vehicle, it doesn¡¯t directly pertain to fully autonomous vehicles. But as full vehicle autonomy is on the roadmap for the automotive industry, functional safety remains mission-critical and the ISO 26262 standard will continue to evolve.

What are the Challenges of ISO 26262?

Some of the challenges of implementing ISO 26262 include:

1. Complexity. The standard is very detailed and covers a wide range of topics, making it difficult to fully understand and implement.

2. Time and Cost. Meeting the requirements of the standard can be time-consuming and costly, and may require significant changes to existing development processes.

3. Testing and Validation. Ensuring that a system meets the requirements of the standard can be challenging, as it may require extensive testing and validation.

4. Risk Assessment. Identifying and assessing potential hazards and risks can be difficult, especially in complex systems.

5. Traceability. Maintaining traceability of requirements and design decisions throughout the development process can be difficult, especially in large and complex projects.

6. Tool Support. There may be a lack of tool support for certain aspects of the standard, making it difficult to fully automate the compliance process.

7. Expertise. Having the necessary expertise and resources to fully implement the standard can be a challenge, as it requires specialized knowledge of functional safety and automotive systems.

What are the Benefits of ISO 26262?

Adopting ISO 26262 helps ensure that the safety of car components is considered from the beginning of the development process. It provides a comprehensive framework for managing safety throughout the entire lifecycle of an automotive component, from initial risk assessment to final decommissioning. By following ISO 26262, automotive manufacturers can ensure that their suppliers are meeting safety standards, preventing costly issues from arising during the production process.

The standard takes into account the trend of increasing integration of hardware and software in automotive electronic systems. It provides detailed guidelines for concurrent development and testing of hardware and software, recognizing that they must be tested together to achieve optimal safety. This ensures that all aspects of the system are considered and tested together, promoting a more comprehensive and thorough approach to functional safety.

Is ISO 26262 Required?

ISO 26262 is not required by law, but many car makers and suppliers follow it to show their commitment to safety and to improve their products safety. Sometimes customers and regulators might require them to prove they follow the standard. But even if it's not required, it's still considered a good practice and following it can improve the safety of car electronic systems and show customers, regulators and end users the company's commitment to safety.