mlns='http://www.w3.org/1999/xhtml'>
Has the industry decided on a definition?
| | How does the industry define a software-defined vehicle (SDV)?
In our August Trends to Watch Report, we revealed findings from our recent SDV survey, indicating ongoing uncertainty about the dominant E/E architecture by 2030.
But stepping back even further, does the industry agree on what a 'software-defined vehicle' actually is? We posed this question to our survey respondents as well: | | | | | | | | | | |
|
|
|
| Software and firmware OTA updates (41%, vehicle data- management capabilities (41%), and centralized, integrated vehicle data infrastructure (38%) are identified as the pivotal elements defining SDVs. OEM respondents place CI/CD (36%) as the third most important SDV element, ahead of centralized data infrastructure (32%). Further analysis reveals two distinct underlying definitions or perceptions of SDVs within the analyzed sample and significant regional disparities. | | The 2024 SDV Survey provides a snapshot of the industry's perspective on SDV technologies, architectures, automaker collaboration, development cycles, and implementation challenges. Subscribe to Wards Intelligence to access the full results. | | |
|
|
|
| | | Maitê Bezerra explores the industry transition to the software-defined vehicle. She follows the evolution toward new electric/electronic vehicle architectures, software development frameworks, revenue streams, and how the automotive supply chain ecosystem is changing. |
|
|
|
Did you catch Maitê discussing the transformative impact of SDVs on the automotive landscape in a recent episode of Altair’s ‘Future Says’ podcast? Listen here if you missed it.
Got a question about software-defined vehicles that requires expert insight? Reach out to WardsAskAnAnalyst@informa.com . |
|
|
|
|
