Title: The Software Foundation Automakers Have Been Seeking Could Be Here
In the annals of automotive history, few periods have been as transformative as the present. Beyond the ongoing shift toward electrification, the rapid race toward the software-defined vehicle (SDV) is reshaping the industry. What began as a seemingly straightforward transition from discrete hardware components to over-the-air (OTA) updatable algorithms has evolved into a complex quagmire of regulatory hurdles and development challenges. The result? A precarious situation where future vehicles might offer fewer features, not more.
Thankfully, a potential resolution is on the horizon. QNX, a leader in hardware virtualization, and Vector, a master of middleware, have joined forces to introduce what they term the Foundational Vehicle Software Platform. If this innovative solution lives up to its promises, it could alleviate many of the most intricate and demanding aspects of automotive software development.
The Shift Toward Software-Defined Vehicles
The term “software-defined vehicle” is not a recent invention. However, as this foundational concept has gained prominence in vehicle design, its meaning has undergone a transformation.
“It’s a term that’s been around for about seven or eight years,” remarks John Wall, President of QNX. “I think in the last few years, it’s really come to signify something very specific. For me, what it truly represents is the vehicle becoming increasingly reliant on software for its features.”
In some automotive organizations, the transition to SDVs has been championed as a panacea for various development woes. The vision is a dramatic reduction and simplification of in-vehicle hardware, coupled with a platform that enables vehicles to maintain their relevance in the market for extended periods.
“I believe one of the primary drivers of the SDV movement in traditional automotive companies is the ability to continually enhance the vehicle over time, introduce new features, and ultimately monetize those new features within the vehicle,” Wall elaborates.
Yet, beneath these aspirational promises lies a concerning reality that has left the software divisions of some manufacturers in disarray.
The Organizational Overhaul That Caught Automakers Off Guard
Achieving new benchmarks in automotive software necessitates more than just advanced coding. For many legacy automakers, it demands a fundamental organizational overhaul.
“Currently, they are struggling, particularly with their development processes,” notes Matthias Traub, a member of the Board of Directors and CTO at Vector. “This struggle extends to the cultural perspective as well. They are accustomed to a clear, waterfall-based development process with well-defined roles.”
The waterfall methodology is a traditional software development approach characterized by linear, sequential phases. This rigid structure proves inadequate in the increasingly dynamic landscape of automotive software.
“Now, the imperative is to transition toward a genuine DevOps approach,” Traub explains. “This involves smaller teams that assume responsibility for the entire development lifecycle—encompassing design, building, software development, testing, and so on.”
Wall concurs, highlighting a misguided belief prevalent among many companies: the conviction that they must develop every line of code in-house. “I think that’s where many of them have faltered,” he states.
The compulsion to own the entire software stack compels developers to write code for even the most rudimentary functions, such as securely transmitting data over the vehicle’s integrated modem or rendering pixels on the display screens. Companies whose core competency is vehicle manufacturing have instead found themselves inundated with layers of software code that their customers will never directly interact with.
“Their energy should be concentrated on features that enhance the customer experience, not on operating systems and networking stacks,” Wall emphasizes.
Compounding the challenge of an ever-expanding software stack is the sheer breadth of modern automotive software regulatory frameworks. The checklist of requirements for developers continues to grow relentlessly.
“You have considerations like the software bill of materials, the provenance of your software—where it originated. There are significant geopolitical considerations, such as what’s occurring in the U.S. and the prohibition of Chinese code,” Wall elaborates. “There are numerous factors to contemplate. It’s a truly dynamic situation.”
Emergence of a Novel Platform
Evolving regulations not only present a moving target for initial compliance but also necessitate ongoing updatability and responsiveness to security vulnerabilities.
“The industry is reaching a tipping point where software complexity threatens to outpace innovation,” Traub warns. If this trend persists, Traub fears that next-generation vehicles may actually possess fewer features than their predecessors.
Complex regulatory environments are an area where QNX has accumulated extensive experience. The company’s foundational operating system is currently deployed in a diverse range of applications, from nuclear power plants to military aircraft.
“Many of the security requirements originated in the medical field, and we encountered them somewhat earlier, influenced by the Biden administration’s initiatives,” Wall recalls.
The Foundational Vehicle Software Platform is built upon this deep well of expertise. It represents a suite of interfaces and tools from QNX and Vector, meticulously designed to streamline modern automotive software development. The platform leverages the historical strengths of both companies in abstracting and simplifying the complexities inherent in integrated systems development. In the automotive context, this translates to providing secure, reliable, and certifiable hardware integration.
“We are endeavoring to eliminate many of these onerous challenges by consolidating them and offering a single source of truth for the platform,” Wall explains.
QNX and Vector have collaborated on various projects for years, but their close partnership on the new platform has spanned the last 18 months. Although still an evolving and ongoing endeavor, the platform is already demonstrating significant promise, not only in terms of simplification but also in performance metrics.
Traub reports that solutions operating on the platform have achieved up to a 50 percent reduction in CPU load compared to custom-written code. Latency—the delay between a system request and the corresponding response—was diminished by 85 percent, while overall data transmission rates more than doubled.
“And we are merely at the beginning,” Traub asserts. “Eighteen months is a relatively short period, and I am confident that further performance acceleration will be realized.”
By optimizing software performance, manufacturers can potentially operate on less complex hardware, thereby reducing vehicle production costs.
A Promising Trajectory, Albeit in Its Early Stages
The Foundational Vehicle Software Platform from QNX and Vector is still in its nascent stages of development. However, by addressing so many of the pain points currently afflicting the modern software industry, it is already gaining significant traction.
“It’s truly remarkable to observe the number of companies inquiring about our solution,” Traub observes. “Previously, our list of interested parties comprised only a handful of names. Now, it has expanded to two handfuls or more.”
The extensive client base of both QNX and Vector ensures that the platform will be refined to meet a wide array of industry requirements.
“Because Vector and QNX collaborate with so many customers globally, we gain comprehensive insight into development roadmaps,” Wall states. “We acquire a clear understanding of the desires of the automotive manufacturers.”
As for the timeline for seeing these innovative solutions integrated into production vehicles, the prospect may be closer than anticipated. “If you had asked me at the outset of this project, I would have projected a 2029 or 2030 timeframe,” Wall concedes. “However, we’ve witnessed an acceleration of progress recently, suggesting that it could transpire sooner than that.”
### 2026 Automotive Software Trends
The automotive industry is currently undergoing a profound transformation, driven by the confluence of electrification and the rise of the software-defined vehicle (SDV). This shift—from traditional, hardware-centric architectures to highly integrated, software-reliant systems—presents both unprecedented opportunities and significant challenges for manufacturers worldwide.
### The Evolution of the Software-Defined Vehicle
The concept of the software-defined vehicle, where vehicle functionality is primarily enabled and enhanced through software, has been evolving for several years. Initially, the vision was to reduce hardware complexity and enable over-the-air (OTA) updates, allowing vehicles to stay relevant longer. However, as this concept has matured, it has become clear that achieving this vision requires more than just software updates; it demands a fundamental rethinking of vehicle architecture and development processes.
According to industry leaders, the true essence of the SDV is the increasing dependency of vehicle features on software. This dependency extends beyond infotainment systems to critical functions such as driver assistance, powertrain management, and connectivity. As vehicles become more software-centric, the complexity of the software stack grows exponentially, creating significant challenges for traditional automakers who are accustomed to hardware-focused development methodologies.
### The Organizational and Cultural Shift
One of the most significant hurdles in the transition to SDVs is the need for organizational and cultural change within automotive companies. Many legacy manufacturers are grappling with the transition from traditional waterfall development processes to more agile, DevOps-oriented approaches.
“Currently, they are struggling, particularly with their development processes,” notes Matthias Traub, CTO at Vector. “This struggle extends to the cultural perspective as well. They are accustomed to a clear, waterfall-based development process with well-defined roles.”
The waterfall model, characterized by linear, sequential phases, is ill-suited for the dynamic nature of software development. In contrast, the DevOps approach emphasizes smaller, cross-functional teams responsible for the entire software lifecycle, from design and development to testing and deployment. This shift requires a fundamental change in mindset and organizational structure.
### The In-House Development Dilemma
Another challenge facing automakers is the misguided belief that they must develop every component of the software stack in-house. This approach leads to an inordinate amount of time and resources being spent on fundamental functions such as data transmission and display rendering, rather than on features that directly enhance the customer experience.
“Their energy should be concentrated on features that enhance the customer experience, not on operating systems and networking stacks,” states John Wall, President of QNX.
The compulsion to own the
