> For the complete documentation index, see [llms.txt](https://www.sdv.guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.sdv.guide/sdv101/part-c-building-blocks/foundation-e-e-architecture/case-study-rivian.md).
# Case Study: Rivian
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.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://www.sdv.guide/sdv101/part-c-building-blocks/foundation-e-e-architecture/case-study-rivian.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.