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

SDV Guide

  • Legal Notice
  • Disclaimer
  • Privacy Policy

(c) 2025 Dirk Slama

On this page
  1. SDV101
  2. Part C: Building Blocks
  3. Foundation: E/E Architecture

Case Study: Rivian

PreviousEvolving Trends in E/E ArchitecturNextStandards for Software-Defined Vehicles and E/E Architectures

Last updated 6 months ago

Rivian, a California-based EV startup specializing in adventure-oriented electric vehicles, provides an insightful example of innovation in E/E architecture. With strong partnerships, including Amazon and Volkswagen, Rivian has made remarkable progress in reducing the complexity of its vehicle architecture, as shared during their Investor Day 2024.

In their first-generation vehicles, Rivian managed to reduce the number of ECUs to just 17, a stark contrast to the dozens typically used by incumbent OEMs. Currently, Rivian is working on its second-generation vehicles, further streamlining the design to only seven in-house developed ECUs.

This architecture employs a region-oriented zonal design, including east, west, and south zonal controllers, complemented by a few specialized ECUs for key functions such as infotainment, AD and ADAS, vehicle access control, and battery management.

The benefits Rivian reports from their Gen 2 architecture are striking:

  • A 60% reduction in the number of ECUs compared to their first-generation vehicles.

  • A 1.6-mile reduction in harness length, significantly reducing vehicle complexity.

  • A weight reduction of 44 pounds per vehicle.

  • A 40% cost reduction in the electrical Bill of Materials (BOM).

This case study underscores how Rivian and other EV startups are embracing zonal E/E architectures, central computing, and software-defined vehicle principles, achieving tangible benefits in cost, complexity, and efficiency. It highlights the competitive edge startups can gain by adopting cutting-edge approaches to E/E systems.