Defining the Software-Defined Future
A new ecosystem of automakers, suppliers and tech companies is converging around the development of the software-defined vehicle. But what exactly defines a software-defined vehicle? And what's the product-development path ahead for the industry as they invest billions of dollars in this transition? The articles and trackers in this Collection seek to answer those questions.
The Rise of the Software-Defined Vehicle
The definition of the software-defined vehicle (SDV) remains in flux, with stakeholders having different interpretations, criteria and expectations. Wards Intelligence defines SDVs as vehicles in which features and functions are enabled primarily or entirely through software. This enables lifecycle management and the delivery of new functionalities over the air (OTA). SDVs offer the flexibility to change key functions and even the nature of hardware through software. Convenience, security, safety, driving performance, and connectivity-related features can be added, altered or upgraded OTA at any time throughout the lifespan of the vehicle. This tracker presents the differences between Semi-SDV and SDV, relationship between SDV and BEVs, and SDVs offered by traditional vs start up manufacturers.
Shifting Gears: Top Priorities for Software-Defined Vehicles
Software-defined vehicles are revolutionizing the auto industry, but with so many elements to consider, it is vital to know where to focus. Wards Intelligence surveyed automakers and other auto industry players to determine the most critical factors.
What Does Auto Industry Gain With SDVs?
A recent Wards Intelligence survey finds three key elements driving the ongoing SDV transformation: the timely OTA introduction of new features; more efficient product development; and the enabling of Level 2+ and Level 3 advanced driver-assistance features. Nevertheless, the results suggest that perceived SDV benefits vary significantly according to a company’s position in the automotive value chain.
You must sign in to use this functionality
Authentication.SignIn.HeadSignInHeader
Email Article
All set! This article has been sent to my@email.address.
All fields are required. For multiple recipients, separate email addresses with a semicolon.
Please Note: Only individuals with an active subscription will be able to access the full article. All other readers will be directed to the abstract and would need to subscribe.