Functional Safety New Vehicle Development: ISO Standards

Product Development Engineering

Functional Safety in Automotive Systems: Standards, Lifecycle, and ISO 26262 Implementation

Applied Philosophy

Introduction: Standards and Lifecycle

In today’s automotive industry, Functional Safety underpins the reliability of complex E/E systems. First, this article reviews the primary standards—ISO 26262, IEC 61508, and ASPICE—that define safety requirements. Then, it explains core concepts such as ASIL, HARA, and the V-model lifecycle. Finally, it explores real-world implementation considerations, including traceability, tool qualification, and change control.

In modern automotive systems, Functional Safety is no longer an option—it is a foundational requirement. Moreover, as vehicles become increasingly software-defined and electronics-driven, the potential for safety-critical failures has grown exponentially. Consequently, the industry has adopted rigorous safety standards and lifecycle processes, led by the globally recognized ISO 26262.

Furthermore, this article aims to align with our series by building on earlier discussions of terminology and business impact. Specifically, we will provide a comprehensive overview of functional safety standards, key concepts such as ASIL and HARA, and the detailed implementation of ISO 26262 across the safety lifecycle—from concept to decommissioning.

Understanding Functional Safety Standards

Overall, to ensure that safety risks are systematically identified and mitigated, the automotive industry adheres to a specific set of standards:

  • ISO 26262: A derivative of IEC 61508 tailored for road vehicles. It addresses the entire safety lifecycle and provides requirements for achieving functional safety in E/E systems.

  • IEC 61508: The broader standard for functional safety across various industries, serving as the foundation for ISO 26262.

  • Automotive SPICE (ASPICE): While not a safety standard, ASPICE supports process improvement and quality assurance for embedded software development and often complements ISO 26262 efforts.

Therefore, by transitioning from conventional safety assurance to formalized frameworks like ISO 26262, organizations benefit from a structured approach to both hardware and software reliability.

Key Concepts: ASIL, HARA, and the V-Model

Fundamentally, three core pillars support ISO 26262 implementation:

  • ASIL (Automotive Safety Integrity Level): First, ASIL classifies risks from A (lowest) to D (highest) based on severity, exposure, and controllability of potential hazards. Higher ASILs demand more stringent development processes and safety mechanisms.

  • HARA (Hazard Analysis and Risk Assessment): Next, HARA identifies hazards, assesses associated risks, and assigns ASIL ratings. This early-stage analysis informs the entire safety lifecycle and guides downstream activities.

  • V-Model Development Lifecycle: Finally, ISO 26262 promotes a V-model that aligns safety requirements, design, implementation, and validation. The left side of the “V” covers planning and specification, while the right side focuses on integration and testing.

Consequently, by integrating ASIL, HARA, and the V-model, teams ensure full traceability, verification, and validation of all safety-related functions.

The Safety Lifecycle Under ISO 26262

ISO 26262 spans ten parts, guiding teams through the full spectrum of functional safety:

  1. Management of Functional Safety (Part 2): First, establish safety organization, roles, and responsibilities.

  2. Concept Phase (Part 3): Next, perform item definition and HARA to derive top-level safety goals.

  3. System Level Development (Parts 4 & 5): Then, translate safety goals into technical requirements and define system architecture.

  4. Hardware and Software Development (Parts 6 & 7): Afterwards, develop components with focus on diagnostic coverage, safe states, and hardware metrics.

  5. Verification and Validation (Parts 8 & 9): Subsequently, execute unit tests, fault injection, and system-level safety validation to confirm compliance.

  6. Production, Operation, Service, and Decommissioning (Part 10): Finally, maintain safety through over‑the‑air updates, change management, and end‑of‑life planning.

Throughout each stage, rigorous traceability and documentation underpin compliance and audit readiness.

ISO 26262 in Action: Implementation Consideration

Implementing ISO 26262 requires cross‑functional collaboration and disciplined execution:

  • Traceability: First, ensure that every safety requirement maps to hardware/software components and associated test cases.

  • Tool Qualification: Then, assess development tools—such as compilers and model checkers—for appropriate safety confidence levels.

  • Change Control: Moreover, evaluate any post‑SOP changes for safety impact and document them as part of a formal safety case.

  • Supplier Engagement: Finally, qualify suppliers and adopt SEooC (Safety Element out of Context) strategies to reuse validated safety assets across projects.

By addressing these considerations, OEMs and suppliers can streamline ISO 26262 implementation and maintain robust safety records.

Conclusion: Functional Safety - Alignment & Next in Series

This article aligns with our overarching series by providing the detailed standards and lifecycle implementation that build on foundational concepts and business case discussions from earlier installments. In the next article, we will focus on how functional safety interfaces with advanced driver-assistance systems (ADAS), sensor fusion, and machine learning.

Series Positioning & Next Steps

  • Real-World Case Studies & Lessons Learned

  • Regulatory Compliance & Supplier Roles

  • Validation & Verification Techniques

  • Functional Safety in EV/ADAS/SDV

  • Emerging Trends: AI & Over-the-Air Updates

Series Index – Functional Safety in Automotive:

  1. Foundations & Frameworks: An ISO 26262 Guide to Automotive Functional Safety: https://georgedallen.com/functional-safety-new-vehicle-development-compliance/
  2. ISO 26262 Design Process: From Safety Goals to Implementation: https://georgedallen.com/why-functional-safety-matters-new-vehicle-development/
  3. ASIL Decomposition and Redundancy Management: ← You are here
  4. Functional Safety Implementation in Vehicle Platforms 
  5. The Role of Functional Safety in ADAS and Autonomous Systems
  6. Why Functional Safety still fails 
  7. Designing for Lifecycle Assurance and Post-SOP Safety Monitoring

Other References:

  1. International Organization for Standardization. ISO 26262: Road vehicles — Functional safety. 2018.
  2. W. Steiner, “ASIL Determination and Application in Automotive Design,” SAE International Journal of Passenger Cars – Electronic and Electrical Systems, vol. 11, no. 3, pp. 175‑183, 2019.
  3. K. Jackson and T. Gallagher, “Design for Functional Safety,” in Advanced Automotive Technologies, Springer, 2020, pp. 45‑68.
  4. S. Chen, “Fault Containment Zones in Automotive Architectures,” IEEE Transactions on Vehicular Technology, vol. 69, no. 5, pp. 5032‑5042, 2020.
  5. Bosch GmbH, “Automotive Safety Handbook,” Bosch, 2021.

Systems Engineering References:

About George D. Allen Consulting:

George D. Allen Consulting is a pioneering force in driving engineering excellence and innovation within the automotive industry. Led by George D. Allen, a seasoned engineering specialist with an illustrious background in occupant safety and systems development, the company is committed to revolutionizing engineering practices for businesses on the cusp of automotive technology. With a proven track record, tailored solutions, and an unwavering commitment to staying ahead of industry trends, George D. Allen Consulting partners with organizations to create a safer, smarter, and more innovative future. For more information, visit www.GeorgeDAllen.com.

Contact:
Website: www.GeorgeDAllen.com
Email: inquiry@GeorgeDAllen.com
Phone: 248-509-4188

Unlock your engineering potential today. Connect with us for a consultation.

Skip to content