
Why the shift to centralized compute threatens the foundations of today’s supplier ecosystem—and what must happen next.
Automotive is entering a structural shift more profound than electrification. The transition from distributed ECUs to centralized and zonal architectures is redefining where intelligence lives in the vehicle, who controls it, and how value is created. The implications are stark: as OEMs consolidate compute into a small number of high-performance System-on-Chips (SoCs), the traditional Tier-1 role as system architect, integrator, and control software owner is rapidly eroding. In its place, a new hierarchy is emerging—one where OEMs and semiconductor platform providers like Qualcomm and NVIDIA dominate the software and compute layer, while many Tier-1s risk becoming suppliers of mechanical assemblies with limited differentiation.
This is the next existential threat facing automotive suppliers. And unlike electrification, which arrived with visible warning signs, the architectural shift is happening quietly embedded in Level 2+ and Level 3 feature roadmaps, hidden in wiring diagrams, and accelerated by OEMs who now see software-defined control as a strategic weapon.
The industry is standing at the threshold of a once-in-a-generation transformation. The question is no longer whether zonal architectures will reshape the value chain—it is whether suppliers will adapt quickly enough to survive the change.
The Architectural Shift: From 100+ ECUs to <10 Domain Controllers
For decades, automotive electronics evolved through organic accumulation: more features required more ECUs, more wiring, and more distributed functionality. The result was a patchwork architecture—complex, redundant, and nearly impossible to update holistically.
Today’s reality is fundamentally different. OEMs are collapsing this sprawl into fewer than ten domain and zone controllers that manage the entire vehicle’s systems, including ADAS, cockpit, engine or battery, body and vehicle.
This transition is driven by three unavoidable forces:
- Level 2 → Level 3 autonomy requirements
L3 systems demand consistent, high-performance compute capabilities, unified perception, and harmonized safety domains. This cannot be achieved through a network of isolated ECUs. - The need for OTA-enabled feature evolution
Distributed ECUs create software incompatibilities, version control issues, and integration complexity. Centralized compute unlocks continuous updates and scalable feature deployment. - Cost, weight, and wiring reduction
Tesla’s roadmap tells the story clearly:
-
- Model S wiring harness: ~3,000 meters
- Model Y wiring harness: <100 meters (even with redundancy)
This structural collapse in wiring length and complexity is not theoretical—it is happening.
OEMs see centralized architectures as the enabler for their long-term software strategies. Like the engine of yesterday, the centralized compute and control stack is the key differentiator for OEMs going forward. Once OEMs take control of the architecture, they inevitably take control of the intelligence that governs it.
The Strategic Reordering of the Value Chain
Under today’s distributed architecture model, Tier-1s have owned the integration layer:
- They delivered ECUs that contained proprietary controls.
- They provided the software and tuning that differentiated system performance.
- They acted as the “glue” between sensors, actuators, and vehicle-level behavior.
This ownership placed Tier-1s at the center of the vehicle value chain. But in a centralized zonal architecture, all of that changes:
- The controls shift from Tier-1 ECUs into OEM-owned (designed and developed) domain controllers.
Steering, braking, thermal, body, comfort, and power distribution systems—once engineered holistically by Tier-1s—lose their software intelligence to the OEM’s centralized controller.
What remains at the Tier-1 level is the:
- Mechanical actuator
- Housing
- Motor/pump
- Commodity hardware interface
In other words: the physical layer, not the intelligence layer.
- The performance differentiation moves up the stack.
OEMs no longer differentiate on chassis hardware or body modules—they differentiate on motion control, energy management, and software-defined features that live in the centralized compute stack including:
- Motion planning
- Redundancy algorithms
- Energy management logic
- ADAS perception and fusion
- Vehicle operating system behaviors
These live in the SoC, not in a distributed ECU.
- Semiconductor companies become the new strategic Tier-0.5.
Qualcomm, NVIDIA, Mobileye, and increasingly AMD and Renesas are now the platforms on which OEMs build their software-defined future. They own the:
- Compute roadmap
- AI acceleration layer
- Middleware
- Real-time operating system environment
This shifts long-term value creation and bargaining power toward silicon providers who can support multi-vehicle, multi-region compute strategies. Tier-1s in this world sit downstream of the decisions that matter most.
The Controls Migration: Why Tier-1 Engineering Value Disappears
Consider chassis systems such as steering and braking or body and comfort systems. These used to be rich engineering domains: control loops, fail-operational logic, diagnostics, sensor fusion, and calibration differentiated one Tier-1 supplier from another. In a centralized compute environment:
- The algorithms migrate into the OEM’s domain controller.
- The safety compute is centralized.
- The motion control stack becomes an OEM asset, integrated with ADAS and automated driving.
- The Tier-1 provides only the actuator and the interface specifications.
This is analogous to removing the brain and leaving only the muscle. Once Tier-1s lose ownership of the system intelligence, the path to differentiation becomes limited. The remaining levers are:
- Cost
- Quality
- Delivery
- Footprint optimization
- Offshore manufacturing strategy
These are not levers that sustain long-term margin expansion.
The Winners: OEMs and SoC Platform Companies
In this future environment, the OEMs are determined to have finally control over the full software stack—a long-standing ambition made possible by simplified architectures. They dictate:
- Compute selection
- Software roadmaps
- Security frameworks
- Data flows
- Motion and energy control strategies
Semiconductor companies will win in this future state because the SoC becomes the central nervous system of the entire vehicle. The vehicle’s long-term capabilities, updates, and differentiation increasingly depend on their roadmap and ecosystem. Thus, a new strategic hierarchy emerges:
OEMs → SoC Platform Providers → All Other Suppliers
This is the most significant shift in supplier–OEM dynamics since the transition from carburetors to electronic fuel injection.
The Path Forward: A Call to Action for Suppliers
The transition to zonal architecture is not a future scenario—it is here, advancing program by program as OEMs lay the foundations for Level 3 autonomy and software-defined vehicles.
Less insightful suppliers who wait for clarity will discover that the architecture has already passed them by.
To remain relevant, suppliers must make four strategic moves now:
- Redefine your role in a world where intelligence lives in the SoC.
If your differentiation comes from controls software that will be absorbed into a domain controller, you must reposition:
- Toward advanced actuation technologies
- Sensing elements tied to zonal strategies, or
- New forms of integration aligned with OEM roadmaps
- Build deep alignment with semiconductor ecosystems.
Suppliers who understand Qualcomm, NVIDIA, or Mobileye architectures will integrate more seamlessly into OEM compute environments. Those who don’t will struggle to meet safety, timing, or integration requirements.
- Pursue mechanical or electromechanical innovation where it creates value.
Even without controls ownership, areas like NVH, packaging, materials engineering, thermal characteristics, and robustness remain important—especially for EV platforms. These must become core strengths, not afterthoughts.
- Restructure cost footprints for a post-ECU world.
As value shifts away from hardware, suppliers must adopt global manufacturing strategies, automation, and modularity to remain competitive in shrinking-margin domains.
Closing: The Architecture of the Future Demands Action Today
Zonal architectures mark a fundamental shift in the automotive value chain—a shift that dismantles long-standing supplier roles, rewrites integration boundaries, and redefines where innovation happens.
The winners of the next decade will not be those who fight to protect legacy ECU-based systems. It will be those who accept that the intelligence has moved, the architecture has changed, and the center of gravity has shifted.
Suppliers who adapt quickly—who reimagine their capabilities, integrate into new software and compute ecosystems, and differentiate where value still exists—will thrive.
Those who do not will be spectators in an industry they once helped define. The time to act is now.




This article highlights a profound transformation in automotive supply chains. The shift from 100+ distributed ECUs to fewer than 10 domain controllers fundamentally changes where intelligence resides in vehicles, empowering OEMs and semiconductor providers while reducing the role of traditional Tier-1 suppliers.
I disagree completely both tautologically and ontologically. I actually think you could not be further from the truth. There has been 100+ distributed ECUs in my car for decades. Sure, they go out sometimes, but I have never had an issue taking my car to the semiconductor provider and having them refreshed. Curious what world you live in where your car doesn’t have more than 10 domain controllers, also.