Ford has scrapped its next-generation electrical architecture, known as FNV4, in favor of a domain-style system that will be used across its entire lineup, including gas and hybrid vehicles. The decision, announced by Ford's software chief Doug Field, comes as the company struggles with stagnant EV sales and project delays.

The FNV4 project, which was aimed at developing a zonal architecture similar to that used by Tesla, was costly and complex, contributing to a $5 billion loss on EVs and software in 2024. Field explained that the world in which Ford started the project is not the same as it is today, with ICE and hybrid vehicles selling at higher rates than electric options. The company has opted for a more incremental approach, adapting its third-generation architecture (FNV3, now rebranded as X.3) to the full range of its lineup.

The domain-style system, which Field admits is "not as elegant" as a zonal architecture, will allow Ford to develop software for a broader range of vehicles. The system will feature a handful of primary ECUs embedded with the most important software code, sending out commands to the rest of the vehicle's microprocessors. This approach will enable Ford to design a system that is compatible with EVs like the Mustang Mach-E, as well as more complex ICE vehicles like the F-150 Super Duty.

Field emphasized that the key to the system is centralizing and consolidating software under Ford's control, ensuring that everything works harmoniously. He drew an analogy to the human brain, explaining that certain functions, like automatic emergency braking, can be centralized, while others, like pinch protection for windows, can be decentralized.

The shift in focus comes as Ford grapples with the challenge of developing software not only for its EVs but also its gas-guzzling, 12V-battery-powered internal combustion engine (ICE) vehicles. Field acknowledged that the company can't leave its ICE and hybrid vehicles "stranded from a digital and software perspective" and focus solely on EVs.

The decision to abandon FNV4 has significant implications for Ford's future software development. The company will need to navigate complex relationships with suppliers and centralize software control to ensure seamless integration. Field expressed confidence in the approach, stating that the goal is to create an amazing software experience in a car that customers love, regardless of the underlying architecture.

The move is seen as a pragmatic response to the current market reality, where EV sales have slowed, and ICE and hybrid vehicles remain dominant. As the auto industry continues to evolve, Ford's decision to prioritize a domain-style system may prove to be a shrewd move, enabling the company to improve its software experience across its entire lineup.