Despite the broader industry shift toward fully software-defined vehicles, Fordis ending development of their FNV4 SDV platform after four years’ work.
The California-based team, led by Doug Field, was originally tasked with developing FNV4 for Ford’s next-generation vehicles. Field says the platform is now being integrated into Ford’s current unified vehicle architecture, to be shared across all models, electric and combustion-powered. The benefits initially intended only for EVs will now also come in combustion-engine vehicles as well.
Zonal architecture is particularly appealing to many automakers due to its ease of implementation and management for both the maker and their suppliers. A single system that manages everything, from the powertrain to safety features and component control, is more attractive than the domain-based architecture currently in use.
The fully networked FNV4 software system was originally designed to improve quality, reduce costs, and enable features like over-the-air updates and paid software upgrades. However, developing software for combustion-powered and hybrid vehicles is significantly more complex than for EVs. A global rollout of FNV4 across all vehicle types would have made it difficult to apply the latest software innovations to traditional engines.
These changes also stem from Ford’s traditionally supplier-based system — a model shared by most established automakers. Unlike EV startups, which develop their software in-house from the ground up, Ford’s software is created by multiple suppliers who often don’t communicate directly with one another.
Even though the software is owned by Ford, developers still have to go through suppliers to request changes to the control software for individual components. This results in project delays and rising costs, contributing to financial losses in Ford’s software divisions—something the company is now aiming to reduce or avoid.
