Software-Defined Vehicle & AI-Defined Vehicle Europe Summit – Frankfurt, March 19
- Luigi Bisbiglia
- 3 hours ago
- 4 min read
If there’s one thing that became clear the moment I opened the day in Frankfurt, it’s this: the automotive industry is no longer just building cars, it’s building software platforms on wheels.
That’s not just a shift in technology. It’s a shift in mindset, in business models and ultimately in what customers expect from their vehicles.
When we talk about Software-Defined Vehicles (SDVs), we’re really talking about a move from static products to dynamic, evolving systems. Much like smartphones, vehicles are now expected to improve over time through updates, new features, and increasingly personalized experiences. The car you buy is no longer “finished” at delivery.
And that matters.
It matters because automakers are under pressure on multiple fronts: faster time to market, increasing software complexity, rising customer expectations, and the need to unlock new revenue streams beyond the initial sale. SDVs promise to address all of these, but they also introduce a new level of complexity that the industry is still learning to manage.
We’ve gone from mechanical vehicles to connected cars, and now into what I would call the “Vehicle 4.0” era defined by centralized computing, scalable architectures, and continuous over-the-air updates. But with that comes a fundamental challenge: how do you balance cost, time, and quality when software is evolving faster than the vehicle lifecycle itself?
One answer that came up repeatedly throughout the day is reducing complexity through architecture.
Service-Oriented Architecture (SOA), hardware-software decoupling, and modular design are no longer “nice to have” they are essential. Without them, the sheer scale of software, often spread across dozens of control units, becomes unmanageable. With them, automakers can move faster, update continuously, and build reusable components across platforms.
This is where the insight really starts to take shape: software is no longer supporting the vehicle it is becoming the primary value driver.
That point was reinforced strongly by Yuzhong Wang, Release Manager at NIO R&D Center, who described SDVs as a true paradigm shift. In the traditional model, vehicles were built around hardware, with fixed features and tightly coupled systems. In the SDV world, software and hardware are decoupled, features are deployed independently via OTA updates, and centralized computing replaces distributed architectures.
But what stood out most was not just the technology, it was the operational implication.
Managing global software delivery at scale is becoming one of the biggest challenges in the industry. Regional variations, whether regulatory, cultural, or technical, can easily lead to fragmentation. NIO’s approach is clear: manage variation through configuration and release control, not through divergent software branches. In simple terms: branches should control releases, not define the product. That’s a subtle but critical shift and one that highlights how software discipline is becoming as important as engineering excellence.
We also saw how this transformation is reshaping the in-vehicle experience itself. The digital cockpit is evolving into the central platform that orchestrates everything from infotainment to vehicle controls to AI-driven services. Artificial intelligence is accelerating this evolution dramatically.
From agentic AI assistants capable of natural, context-aware conversations to hyper-personalized interfaces that learn driver preferences, the cockpit is becoming less of a dashboard and more of an intelligent companion. Advanced analytics are enabling predictive maintenance, driver insights, and fleet optimization, while AI is also transforming development processes through automated testing and debugging.
A great example of this is NIO’s NOMI system. What started as a voice assistant has evolved into something much closer to a digital companion capable of real conversations, proactive assistance, and increasingly human-like interaction.
With the introduction of NOMI GPT, the boundary between user interface and user relationship is starting to blur.
And that raises an important question: are we designing features, or are we designing experiences? Because the winners in this space will not be those who simply add more functionality, but those who create seamless, intuitive, and emotionally engaging interactions.
Of course, none of this comes without challenges.
From a technical perspective, the scale of software complexity is immense. Leo Hendrawan from QNX highlighted the importance of foundational platform choices, particularly microkernel-based architectures that can provide reliability, safety and cybersecurity in centralized, high-performance computing environments.
From an ecosystem perspective, open standards and collaboration are critical. Technologies like POSIX and VirtIO enable interoperability and portability, but they also require strong governance and alignment across stakeholders.
From a regulatory perspective, the stakes are even higher. Data compliance, especially for global players, is becoming a defining factor. As highlighted by Dr Yang Song, Senior Solution Architect at Alibaba Cloud, companies operating across Europe and China must navigate dual jurisdictions, cross-border AI training constraints, and strict data governance requirements. In this context, compliance is no longer a back-office concern and it directly impacts time to market and competitive positioning.
Even the choice of software platforms reflects this tension. Marius Mailat, CTO at P3 Group, described how Android Automotive OS, for example, offers scalability, reusability, and faster development cycles through its open-source foundation. At the same time, the distinction between Google Automotive Services (GAS) and non-GAS solutions highlights the trade-off between openness and commercial ecosystems.
So where does all of this lead?
If I had to summarize the day in one key message, it would be this: the future belongs to organizations that can master software delivery at global scale. Not just build great software, but deliver it continuously, reliably, and compliantly across markets, platforms, and lifecycles.
Key takeaway
The car is no longer a product: it’s a platform! And success will depend on how well companies can turn that platform into a continuous source of value, for both the customer and the business.
“Software is no longer an enabler in automotive: it is the product, the experience, and increasingly, the business model itself.”
To explore how these trends impact your strategy and operations, we invite you to get in touch for a deeper discussion. Email info@sbdautomotive.com to connect with one of our team of experts to discuss your requirements further.
Trends, challenges & reflections
Software-defined architectures are shifting value from hardware to continuous digital services
AI is redefining the in-vehicle experience, moving from interface to intelligent companion
Global scale brings complexity: regulatory compliance, regional variation, and ecosystem fragmentation
The real differentiator will be the ability to deliver software consistently, securely and continuously across the vehicle lifecycle