In the biggest news of all, Rivian and Volkswagen announced a $5 billion joint venture that will co-develop core parts of the hardware and software platform to be used in cars from both automakers.
We love that because it aligns so beautifully with our mission: the ability to help accelerate putting highly compelling electric vehicles into the market, which will ultimately drive more demand.
A core objective of how we’ve structured the joint venture is that we don’t lose the velocity and the speed and the decisiveness and lack of bureaucracy that exists within our software function today.
Beyond just simplification of how we manage running over-the-air updates across so many different instances, it also gets us a lot of supply chain leverage in a way that we, Rivian, haven’t had in the past.
In fact, you can imagine the day of the announcement, I had a handful of phone calls from CEOs of big semiconductor suppliers, and they’re like, “Hey, we can work harder on pricing.” So, that was awesome.
So, taking away all those mechanical design studio packaging constraints that we had before, and then solving the biggest challenge, which was network architecture by this being that as a project, it’s just a very different type of relationship.
The original article contains 11,459 words, the summary contains 210 words. Saved 98%. I’m a bot and I’m open source!
This is the best summary I could come up with:
In the biggest news of all, Rivian and Volkswagen announced a $5 billion joint venture that will co-develop core parts of the hardware and software platform to be used in cars from both automakers.
We love that because it aligns so beautifully with our mission: the ability to help accelerate putting highly compelling electric vehicles into the market, which will ultimately drive more demand.
A core objective of how we’ve structured the joint venture is that we don’t lose the velocity and the speed and the decisiveness and lack of bureaucracy that exists within our software function today.
Beyond just simplification of how we manage running over-the-air updates across so many different instances, it also gets us a lot of supply chain leverage in a way that we, Rivian, haven’t had in the past.
In fact, you can imagine the day of the announcement, I had a handful of phone calls from CEOs of big semiconductor suppliers, and they’re like, “Hey, we can work harder on pricing.” So, that was awesome.
So, taking away all those mechanical design studio packaging constraints that we had before, and then solving the biggest challenge, which was network architecture by this being that as a project, it’s just a very different type of relationship.
The original article contains 11,459 words, the summary contains 210 words. Saved 98%. I’m a bot and I’m open source!