Open ADx Manifesto Q&A
To get first-hand insight, we sat down with Andreas Riexinger. Andreas is a product manager for autonomous driving at Robert Bosch GmbH and chair of the OpenADx Working Group Steering Committee. He was involved in developing the OpenADx Manifesto and is a committer to the Eclipse Cloe and Eclipse iceoryx projects.
Here’s an edited version of our conversation.
Q. Why was the OpenADx Working Group created?
A. A few years ago, when companies started working on autonomous driving (AD) technologies, everyone was developing their own toolchain. The toolchain is something everyone needs, but it’s not a competitive differentiator and everyone was using similar tools anyway.
So, we saw the opportunity to stop wasting time and duplicating effort by joining forces to collaborate on toolchain technologies in an open environment so we could share costs and risks. The OpenADx Working Group at the Eclipse Foundation is where we do that.
Q. What types of companies are involved in the OpenADx Working Group?
A. We currently have quite a few different domains represented in the working group.
- We have companies such as Bosch and Denso, which are quite well-known in the automotive industry.
- We have tool vendors, such as AVL, because they want their tools to meet as many user needs as possible out of the box without having to customize them.
- We also have infrastructure and IT giants such as Microsoft and Red Hat.
- We have engineering services providers, such as EclipseSource, ADLINK, which is an edge computing and IoT solutions company, and consulting companies.
- In addition, we have the Dortmund University of Applied Sciences and Arts and two other open source foundations: Open Robotics and The Autoware Foundation.
- We have other members as well. The complete list is available on our website.
So, it’s quite a diverse group of organizations. They bring a broad perspective to our efforts, which is good for the industry and for the open source technologies we’re developing.
Q. What are the goals of the OpenADx Working Group?
A. One of our main goals is to develop an interoperable toolchain where everyone can plug in their own toolchain or their preferred tool. The toolchain model is adaptable to each company’s tools and way of working.
If you look at the development chain, everyone needs to complete the same tasks, starting with the architecture definition and moving through other steps until you jump in the vehicle to test drive it and validate the connectivity. The illustration below shows an example of the development chain we are using.
Companies have already invested heavily in licenses and employee training for the tools they’re using at each stage of development. It’s simply not feasible to define just one toolchain and force everyone to use the same tools.
This is why we’re focusing on the data models and the interfaces between the tools. With a reference architecture for interoperability, it will be easier for companies to exchange tools, and to use their preferred tools.
Q. Does the OpenADx Working Group focus on technologies beyond the toolchain?
A. Yes. In addition to the toolchain, we’re focusing on:
- The software stack and its reference architecture for interoperability
- Infrastructure such as the integration backend
We’re aiming to have everything hosted in the cloud. This will ensure that technologies are always up-to-date and accessible by everyone, from everywhere, with no need to install software locally.
Q. How does the OpenADx Working Group relate to the other automotive working groups and technologies at the Eclipse Foundation?
A. We collaborate with other Eclipse Foundation working groups and projects that focus on areas that are relevant for the OpenADx Working Group. This illustration captures it well.
In addition, we collaborate with organizations such as the Association for Standardization of Automation and Measuring Systems (ASAM), which is also an Eclipse Foundation member. The Association is a non-profit organization that promotes standardization for toolchains in automotive development and testing.
Q. Looking ahead, is there an opportunity for the OpenADx Working Group to focus on the differentiating aspects of automotive development one day?
A. About five years ago, talking about open source software in the automotive industry was more or less a no-go. But things are changing and from my point of view, they’re on the right track.
For example, the automotive parts manufacturing company, Continental, uses an open source tool for research and development. Audi has open sourced some of its testing equipment. Tesla has open sourced some of its Model X and Model S code. And the U.S. Department of Transportation Federal Highway Administration has developed the CARMA Platform, which is an open source software platform for testing and evaluating cooperative automation concepts.
To really focus on open source software in differentiating areas, the mindset in the automotive industry needs to change more. But there are good opportunities for companies to innovate on top of open source and build business models around it.
For example, the traffic jam pilot or the highway pilot could use open source base communications mechanisms. Or a company could provide ISO 26262 artifacts and certification services for tools that leverage open source software and must be certified.
Q. What will it take to change the mindset toward open source in the automotive industry?
A. It will take more people understanding that open source has an important role to play in the automotive industry. It’s not a threat. It’s a chance to save money, share risks, and reduce risks. And there are business opportunities associated with it.
Q. How can people get involved in the OpenADx Working Group and projects?
A. There are no hurdles. Everyone is invited to use the results of our work and participate in the community, even if they’re not members of the Eclipse Foundation. If they would like to help shape the direction of the OpenADx Working Group, then they should become members of the Eclipse Foundation and the working group.
Feel free to use our mailing list to start a discussion or become part of one.
To learn more about the benefits of becoming an Eclipse Foundation member, visit the Members page.