Finding
Central compute replaces dozens of single-purpose controllers with a few powerful computers, which makes software ownership and OTA practical
Conventional vehicles carry 40 to 150 electronic control units (ECUs), each from a supplier and each with its own software, according to Rivian. Updating or securing all of them is slow and costly. Software-defined designs consolidate functions onto one to three high-performance computers - typically one for driver assistance, one for infotainment and one for vehicle functions - with zonal controllers handling local inputs and outputs. Rivian's Gen 2 R1 runs on seven ECUs, down from 17.
Consolidation demands partitioning: a hypervisor or separate cores keep a safety-critical brake function isolated from a media player crash, and redundant compute or power paths protect functions that must not fail. The same pattern applies to robots (one controller per robot instead of per joint group), depots (one site controller instead of per-charger logic) and factories (edge servers instead of isolated PLC programs).
Roles
What central compute does
| Role | Example | Requirement |
|---|---|---|
| Real-time control | Torque, braking, joint control | Deterministic timing, safety certification |
| Autonomy and perception | Driver assistance, robot vision | AI accelerators |
| Coordination | Charging, thermal, power sharing | Access to all zones |
| Data and OTA | Telemetry, update management | Storage, secure boot |
| Isolation | Separate safety and non-safety software | Hypervisor, separate cores |
Sources
Sources and scope
- Scope
- SDS Central Compute
- Sources
- Rivian (2024); ElectronsX
- Updated
- October 2026