SDV Guide
digital.auto
  • Welcome
  • SDV101
    • Part A: Essentials
      • Smart Phone? No: Habitat on Wheels!
      • Basics: What is a Software-defined Vehicle
      • MHP: Expert Opinion
      • Challenges: What sets automotive software development apart?
      • SDV Domains and Two-Speed Delivery
    • Part B: Lessons Learned
      • Learnings from the Internet Folks
        • Innovation Management
        • Cloud Native Principles
          • DevOps and Continuous Delivery
          • Loose Coupling
            • Microservices & APIs
            • Containerization
            • Building Robust and Resilient Systems
      • Learnings from the Smart Phone Folks
    • Part C: Building Blocks
      • Foundation: E/E Architecture
        • Today`s E/E Architectures
        • Evolving Trends in E/E Architectur
        • Case Study: Rivian
      • Standards for Software-Defined Vehicles and E/E Architectures
      • Building Blocks of an SDV
        • Service-Oriented Architecture
          • The SOA Framework for SDVs
          • Container Runtimes
          • Vehicle APIs
          • Example: Real-World Application of SDV Concepts
          • Ensuring Functional Safety
          • Event Chains in Vehicle SOAs
          • Vehicle SOA Tech Stack
        • Over-the-Air Updates: The Backbone of Software-Defined Vehicles
        • Vehicle App Store: The Holy Grail of Software-Defined Vehicles
      • Summary: Building Blocks for Software-Defined Vehicles
    • Part D: Implementation Strategies
      • #DigitalFirst
      • Hardware vs Software Engineering
        • The Traditional V-Model in Automotive Development
        • Agile V-Model, anybody?
        • Key: Loosely Coupled, Automated Development Pipelines
        • The SDV Software Factory
      • Implementing the Shift Left
        • Simulation and Digital Prototyping
          • Early Validation: Cloud-based SDV Prototyping
          • Detailed Validation: SDVs and Simulation
        • Towards the Virtual Vehicle
          • Case Study: Multi-Supplier Collaboration on Virtual Platform
          • Long-Term Vision
        • Physical test system
        • De-Coupled, Multi-Speed System Evolution
        • Continuous Homologation
        • Summary and Outlook
      • Enterprise Topics
        • Variant Management
        • Engineering Intelligence
        • Enterprise Organization, Processes, and Architecture
        • Incumbent OEMs vs EV Start-ups
  • SDV201
  • ./pulse
    • SDV Culture
    • Lean Sourcing
      • LeanRM
        • Why so many Requirements?
      • SCM for SDVs
    • SDV Systems Engineering
      • LeanSE
      • SDVxMBSE
    • Digital First
    • Loose Coupling
      • API-first
      • Freeze Points
    • Automation and Engineering Intelligence
    • Continuous Homologation
    • Build / Measure / Learn
  • Glossary
Powered by GitBook
On this page
  • SDV Domains
  • AD/ADAS
  • Motion
  • Energy
  • Body & Comfort
  • Vehicle Experience
  • Infotainment
  • Value-Added Services
  • SDV Domains: Summary
  • Two-Speed Delivery Model
  • Aligning Speed with Safety Requirements
  • Optimizing Resource Allocation
  • Ensuring Smooth Integration
  • Balancing Innovation and Compliance
  • Mitigating Risks Effectively
  1. SDV101
  2. Part A: Essentials

SDV Domains and Two-Speed Delivery

PreviousChallenges: What sets automotive software development apart?NextPart B: Lessons Learned

Last updated 6 months ago

SDV Guide

  • Legal Notice
  • Disclaimer
  • Privacy Policy

(c) 2025 Dirk Slama

SDV Domains

Let us now explore the different Software-Defined Vehicle (SDV) domains, and how they can best be supported by a Two-Speed Delivery Model. The main vehicle domains include AD ADAS, Motion, Energy, Body & Comfort, and Vehicle Experience, encompassing Infotainment and Value-Added Services.

Each domain contributes unique functionalities and carries varying levels of safety-critical requirements, categorized into ASIL and QM ratings.

AD/ADAS

The AD/ADAS (Automated Driving / Advanced Driver Assistance Systems) domain includes systems like:

ASIL Functions:

  • Lane Keeping Assist: Maintains the vehicle within lane boundaries.

  • Adaptive Cruise Control: Maintains speed and distance relative to other vehicles.

  • Fully Automated Driving: Self-driving capabilities requiring robust functional safety.

  • Electric Power Steering: Essential for precise control and safety.

QM or ASIL-A Functions:

  • Camera Display Systems: Provides visual alerts about vehicles in blind spots. These are rated QM or ASIL-A as they only inform the driver without taking corrective action.

  • Traffic Sign Recognition: Detects and displays signs like speed limits for driver awareness, typically QM or ASIL-A due to limited safety implications.

  • Basic Parking Assist: Alerts the driver of nearby obstacles but does not intervene in steering or braking, making it QM or ASIL-A.

Motion

The Motion domain focuses on core driving and vehicle control functions.

ASIL Functions:

  • Anti-Lock Braking Systems (ABS): Prevents wheel lock during braking.

  • Electronic Stability Control (ESC): Maintains vehicle stability during maneuvers.

  • Brake-by-Wire Systems: Replaces mechanical braking with electronic systems.

  • Electronic Power Steering (EPS): Ensures precise steering control.

QM or ASIL-A Functions:

  • Powertrain Modes: Eco or Sport driving settings enhance user experience without impacting safety-critical systems.

  • Non-Critical Drivetrain Adjustments: Torque distribution or shift patterns for improved driving feel.

  • Suspension Settings for Comfort: Adjustable modes like soft or firm improve ride quality.

  • Cosmetic Bumpers: Provide minor protection and aesthetics but are non-safety-critical.

Energy

The Energy domain differs significantly across electric, hybrid, and combustion vehicles.

ASIL Functions:

  • Battery Management Systems (BMS): Monitors and controls battery performance.

  • High Voltage Distribution Systems: Ensures safe power delivery.

  • Thermal Management Systems: Regulates operating temperatures.

  • Regenerative Braking: Recaptures energy during braking.

  • Onboard Charging Control: Manages electric vehicle charging processes.

QM or ASIL-A Functions:

  • Battery Charge Level Display: Provides status without impacting safety.

  • Auxiliary Power Management: Controls non-critical electrical systems.

  • Solar Panel Integration: Enhances energy efficiency but is non-safety-critical.

Body & Comfort

The Body & Comfort domain spans structural and convenience features, with safety-critical and non-critical elements.

ASIL Functions:

  • Seat Belt Pre-Tensioners: Tighten belts during crashes for occupant safety.

  • Airbag Systems: Deploy to protect occupants during collisions.

  • Door Locking Systems: Maintain security and safety.

  • Active Head Restraints: Minimize whiplash injuries.

  • Pedestrian Protection Systems: Reduce injury risks in collisions.

QM Functions:

  • HVAC (Heating, Ventilation, and Air Conditioning): Maintains cabin comfort.

  • Power Seat Adjustments: Customizes seating positions.

  • Sunroof Operations: Adds convenience without impacting safety.

  • Power Windows and Mirrors: Enhances usability.

Vehicle Experience

The Vehicle Experience domain focuses on overall user experience, primarily rated QM.

QM Functions:

  • Personalized Settings: Tailored user profiles for comfort and convenience.

  • Passenger Welcome Sequences: Algorithms that adjust the seat and open doors based on user preferences.

These QM algorithms often interact with ASIL-rated systems through safe APIs. For example, a welcome sequence algorithm may open doors (ASIL-rated) but remains non-critical itself.

Infotainment

The Infotainment domain enhances the driving experience through connectivity and entertainment features, generally rated QM.

QM Functions:

  • Audio Systems: Manage sound entertainment.

  • Navigation Systems: Provide real-time routing and traffic updates.

  • Media Controls and Displays: Offer user-friendly interfaces for controlling media.

  • Smartphone Integration: Connects mobile devices to the vehicle.

Infotainment warnings (e.g., attention prompts) inform drivers but do not control safety-critical systems, keeping them out of the ASIL domain.

Value-Added Services

The Value-Added Services domain focuses on convenience and innovation, also primarily rated QM.

QM Functions:

  • Subscription-Based Features: Unlockable digital services.

  • Non-Critical Predictive Maintenance: Offers proactive notifications without safety implications.

  • Smart Home Integration: Connects vehicles to home automation systems.

  • E-Commerce and Sustainability Services: Adds functionality without affecting safety.

SDV Domains: Summary

Each domain maps differently to the ASIL vs. QM framework:

  • ASIL-Dominant: AD ADAS, Motion, Energy.

  • QM-Dominant: Vehicle Experience, Infotainment, Value-Added Services.

  • Mixed: Body & Comfort.

Two-Speed Delivery Model

Implementing a two-speed delivery model for Software-Defined Vehicles (SDVs) requires a clear understanding of QM and ASIL ratings to effectively balance fast innovation with safety compliance. This approach ensures seamless integration and efficient resource allocation while addressing both safety-critical and non-critical domains.

Aligning Speed with Safety Requirements

  • QM Systems: Enable faster iterations and agile development for non-critical features.

  • ASIL Systems: Require rigorous, slower validation processes to meet functional safety standards.

Optimizing Resource Allocation

  • Agile Teams: Focus on QM domains to accelerate development cycles.

  • Specialized Teams: Handle safety-critical ASIL systems, ensuring compliance and robustness.

Ensuring Smooth Integration

Differentiating QM and ASIL ratings avoids conflicts between safety-critical and non-critical domains, enabling:

  • Clear separation of development workflows.

  • Harmonized interactions across domains.

Balancing Innovation and Compliance

Encourage rapid development in QM areas while maintaining stringent safety standards for ASIL-rated functions. This dual approach fosters:

  • Continuous innovation.

  • Regulatory compliance.

Mitigating Risks Effectively

Fast updates in QM domains are carefully managed to ensure they do not compromise the reliability of ASIL systems. This minimizes risks while maximizing flexibility.

The two-speed delivery model enables SDV developers to address the diverse requirements of modern vehicles, combining agility and safety to drive innovation without sacrificing reliability.

By aligning development strategies with domain-specific requirements, OEMs can optimize both user experience and functional safety.