Collaboration in the software-defined vehicle (SDV) space is not just a best practice; it’s a necessity. As the automotive industry shifts toward software-driven innovation, the role of open source becomes pivotal. However, fostering collaboration in a historically siloed industry presents both immense opportunities and significant challenges. At Open Community for Automotive last fall, experts Kai Hudalla, Steven Hartley, Phani Gangula, and Carlton Bale shared their insights on why collaboration and integration are so critical – and so difficult – in the SDV ecosystem.
Why Collaboration Matters
Kai Hudalla, Open Source Advocate at ETAS, succinctly captures the importance of collaboration in open source SDV: “This is the most important part for the success of any of these technologies.” He emphasises that much of the technology in the SDV domain is generic and not tied to domain-specific problems. Developing these foundational components independently – as has been the norm in the automotive sector – is inefficient and redundant. By pooling resources and expertise, companies can avoid reinventing the wheel and accelerate innovation.
Steven Hartley, Director of Product Engineering at BlackBerry QNX, highlights another dimension of collaboration: integration. “By integrating these projects with each other, it gives you an opportunity to demonstrate how the technologies can be blended across each other,” he explains. Projects like Eclipse Zenoh and Eclipse uProtocol exemplify how contributors from diverse organisations such as Zettascale, Bosch, and ETAS are working together to create interoperable solutions. This integration not only enriches the ecosystem, but also expands the pool of contributors, fostering a more vibrant and diverse community.
The Challenges of Collaboration
While the benefits of collaboration are clear, the path is fraught with obstacles. Hudalla underscores the cultural shift required in the automotive sector, where collaboration traditionally occurred through NDAs and closed-door agreements. “Finding a valid collaboration model is very challenging,” he notes. Companies must embrace open source’s transparency and shared ownership – a stark contrast to the legacy closed-source environment.
Safety requirements present another hurdle. Integrating open source development practices with rigorous safety standards is an ongoing challenge. Though efforts are underway (e.g. through our Automotive Processes SIG), achieving full alignment remains elusive.
Hartley points out that resistance to open source often stems from cultural inertia. However, he argues that open source collaboration delivers substantial benefits: “From a productivity and quality level, it’s so much better because of the expectations that everyone can see your code. You want to put your best foot forward and make sure it’s of the highest quality.” Adopting this mindset can enhance both open and closed-source projects within the automotive ecosystem.
Integration in Action: Success Stories
The Importance of Proactive Outreach
Phani Gangula, Senior Solutions Architect at Zettascale, shares a compelling example of successful collaboration through the Eclipse Fleet Management Blueprint – an example that demonstrates how important it is to proactively reach out to committers beyond one’s own project and company. By proposing the integration of Eclipse Zenoh as a communication backbone – replacing MQTT – his team demonstrated the tangible value of collaboration. After discussions and code reviews with Eclipse Kuksa committers, the integration was accepted, paving the way for new Blueprints like the Service to Signal Blueprint. “Talking to other committers, coordinating how we can add value through this kind of integration led to this collaboration,” he recalls, urging others to embrace similar outreach.
Communicating the Benefits: Cost-Effectiveness, Standardisation
Carlton Bale, Director of Connectivity Strategy at Cummins, provides another powerful example involving Eclipse Kanto and Eclipse CANought. Together, these projects address two critical challenges in vehicle software updates: running the updater application on telematics devices and providing secure, standardised access over CAN to embedded ECUs. Open source solutions like uProtocol and uServices enable seamless integration across various components, delivering a cost-effective, standardised approach to software updates. Bale notes that these solutions work “across all makes and models of equipment”, highlighting the scalability and versatility of open source collaboration. Carlton’s example shows how important it is to raise awareness of the benefits of project collaboration, e.g. cost-effectiveness, standardisation, or seamless solutions. And let’s not forget the fun of working with diverse project teams from various companies, industries and countries!
Building the Future of SDVs Together
Collaboration and integration are the twin pillars of progress in the SDV field. By embracing open source principles, the automotive industry can overcome historical silos and unlock unprecedented innovation. As Hudalla, Hartley, Gangula, and Bale demonstrate, the path is not easy, but the rewards – accelerated development, higher quality, and a stronger community – are worth the effort.
For those considering stepping into the world of open source SDV, the message is clear: the time to collaborate is now. By working together, we can shape the future of mobility.
