Skip to main content
Jump to: navigation, search

Difference between revisions of "OpenADx"

m (Workshop 3, Oct. 23rd, 2017 (Ludwigsburg, Germany) - Planning)
Line 69: Line 69:
* Bosch
* Bosch
* Microsoft
* Microsoft
* itemis
=== Communication ===
=== Communication ===

Revision as of 16:04, 20 October 2017

Welcome to OpenADx

Automated Driving (AD) is clustered into three equally important technology areas:

1) In-vehicle technology

2) Cloud technology (backend)

3) Design, development, test and validation tools (tool chain)

OpenADx is focused on the AD tool chain. The goal is to accelerate AD development through open collaboration and open source.

OpenADx' vision is to ensure transparency and make the complex AD tool landscape more easily accessible for enterprise users.


AD is a complex challenge and therefore requires a multifaceted development process incorporating a variety of software tools. The tools the industry currently uses are very good, but they don’t seamlessly work with one another. This is a result of the tools not being designed to work together. This is an industry-wide issue that slows us down in the race to AD development. By pooling resources, we can remove the “friction” between widely used tools. We can create something of use to all of us: open, compatible and accessible.

OpenADx Grafiken weiß 72dpi Automated driving is a complex challenge.jpg

Problem and benefits for OEMs

User insight: "Developing automated driving functions is extremely complicated and requires the use of many complex software tools which do not work efficiently with one another. What I need is a set of tools which work with each other seamlessly so that my teams can move through the development process more quickly and efficiently."

Benefit: The automated driving tool chain allows your team to work together more efficiently with a suite of highly integrated tools by enabling seamless transfer of data and code through each step of the automated driving development process.

Problem and benefits for tool providers

User insight: "Currently, tools used to create automated driving applications do not work efficiently with one another. If our tool is compatible with other widely used SW tools, it will ease the development process for our customers and make our products even more attractive to them."

Benefit: The seamless integration of your software tool in the automated driving tool chain makes it more attractive to organizations developing automated driving applications by increasing their development efficiency.

Integrated tool chain for AD system development

Leveraging the current tool landscape and tying in players from industry and academia is a must. Therefore, our approach is two-fold. First, we will fine-tune the development tool chain to the needs of our industry. We do this by integrating existing products in the market, adjusting existing tools to our needs, and developing additional tools through Open Source Software (OSS) where none today currently exist. Second, we will bring areas of expertise together in order to make the complex AD tool landscape more easily accessible for all stakeholders.

OpenADx Grafiken weiß 72dpi Integrated toolchain for AD system development .jpg


We believe an initiative like this should be inclusive, not exclusive. It’s about removing barriers to efficient development with widely established tools. It’s about bundling industry competencies and sharing development. We plan to demonstrate our ability to work together on joint testbeds in an open source setting. This allows potential partners to engage with a limited initial investment. The testbeds produce demonstrable results and strengthen confidence in the approach.

The Idea of Testbeds

Testbeds are setup to produce demonstable results that incubate potential open source projects. To realize a testbed the idea is to execute so called Hack-Fests which assemble at least 5 developers for up to 10 days to produce a prototype that solves a use case in the AD environment.

To identify testbed candidates, everybody is invited to propose ideas here to build a starting point for development of the idea towards the requirements for the execution of a Hack-Fest and for winning further interested parties.

To execute a Hack-Fest, we have identified these minimum requirements to make this a fruitful event:

  • A minimum of two partners collaborating on the testbed, be it companies, universities or research organizations
  • A minimum of 5 committed participants for 5 to 10 working days each

Workflow for testbed candidates

  1. Verbalization of a task in use case form, which has potential for further work
  2. Contribution of the use cases by interested partners as testbed candidates
  3. Preparation of the testbed candidates in one or a series of workshops to a state that is sufficient for the participants of a HackFest to produce results
  4. Execution of the Hack-Fest
  5. Evaluation of the Hack-Fest results to decide on whether to follow the idea or to stop the effort
  6. Reworking the Hack-Fest results to build a contribution either to an existing project or as an initial contribution of a new open source project

Who We Are and How to Join

The initiative is still in an early stage, but more then twenty organizations have already shown interest. As we have a public website now it would be nice to give newcomers an understanding who is involved and how to interact with us.

Interested Parties

Please add the name of your organization if you are interested in OpenADx or tell us to do it for you.

  • Bosch
  • Microsoft
  • itemis


  • We have a mailing list: Subscribe for news and discussions: Mailing list
  • We have workshops with introduction sessions and have just started to work on concrete testbeds to identify topics that we agree to collaborate on. The next workshop is Oct 23rd in Ludwigsburg, Germany. Meet us there: Eclipsecon Europe Automotive Unconference

Testbed Candidates

Candidate 1: Simulation


The challenge in the simulation of AD functions is the big amount of test cases which can be easily generated by variation of parameters. This big amount of test cases should be handled with parallel execution of every single test case on the simulation environment.

Description / Goal

To solve the challenge described above, there is the need for a simulation environment, which is scalable. This means, the simulation task for a single test case should be send to a configurable container which is able to execute in parallel to other container executions on a server farm or in a cloud environment.

The hardware / load management of the server farm / cloud infrastructure should be done by itself, so that the only user task is to define how many containers (numbers of test cases) he needs. This ensures an easy operation from simulation engineers point of view.

All used data (input as well as output) in this development step (simulation) have to be available in an usable / standardized format to ensure exchangeability. The data format should be standardized and have to support measurement data as well as simulation data and results. This is necessary to bring the same kind of data to the next development step, e.g. data analytics with big data approaches.

The results of the simulation have to be linked to the subsequent evaluation system as well as to requirements and test management system. The evaluation must be able to generate reports.

The solution should incorporate already existing approaches, i.e. integration of technologies like Eclipse SUMO, OpenPASS, OpenMDM, OpenDRIVE, OpenScenario, OpenCRG , Open Simulation Interface, AirSim, ROS, Pegasus

Technology View


Planned Work Packages

Work Package 1 – Big Picture

Work Package 2 – Scalable Simulation Runtime

Prototype a scalable environment, in which simulation engines can run with high performance in parallel

Work Package 3 – Open Scenarios

Start a database with configurable base scenarios, e.g. roundabouts in a standardized way, so that everyone can use these scenarios

Work Package 4 – Common Data Formats

Evaluate existing data formats, identify gaps and fill the gaps prototypically

Work Package 5 – Visualization

Prototype visualization of all simulation results in one overview, e.g. if possible, show 100 simulation results in one window, if you have 100 test cases

Candidate 2: Massive data ingest and management


Developing and validating AD functions requires the collection of data from various sensors, actuators and other sources. This ideally takes place in a fleet operation. However, due to the required scale and diversity of measurement systems, the AD community faces a massive amount of complex and heterogeneous data.

Descriptions / Goal

This Challenge, i.e. AD data, fulfills all aspects of 'Big Data'. It is of massive volume, there exists a large variety, it is recorded in a high velocity, and usually exists in various formats. However, most available, automotive systems for handling data captured in such an environment cannot process this data in an efficient workflow. Additionally, there exists a painful gap between measurement system and tools, and data analytics and processing platforms.

To solve this challenge, there is the need for a common and open-source handling of measurement data. This should ideally be in the form of common ETL processes, which fill the gap between the heterogeneous measurement data and a suitable backend that already as an industry standard for data analysis.

This solution should incorporate the various formats such as ADTFs .dat, ROS .bag, Vectors .mdf, ...

Suggested work packages

Work package 1 - Problem space

Understand all necessary aspects to clearly define a common problem space. The above the description of the challenge may only cover some parts and is only in the perspective of one stakeholder.

Work package 2 - ETL

Start a sample ETL implementation that provides an efficient ingest of ROS .bag files into a Hadoop environment.

Work package 3 - Data management

Evaluated what is needed to manage this massive, heterogeneous and globally distributed data.


Workshop 3, Oct. 23rd, 2017 (Ludwigsburg, Germany) - Planning

The workshop will take place on the Unconference day of Eclipse Con Europe 2017. Interested participants should register to the unconference day to get access.


  • 08:30 - 09:00: Welcome Coffee and Registration
  • 09:00 - 12:30: Automotive Unconference including an introduction of OpenADx
  • 12:30 - 14:00: Lunch and Poster Session
  • 14:00 - 17:30: Working sessions on OpenADx testbed candidates
  • 17:30 - 18:30: Meet & Greet

Planned sessions for testbed candidates (please add your session!):

  • Testbed candidate 1 (simulation), Lars Geyer-Blaumeiser (Bosch):
    • Clarify further detail for work package 1, i.e., getting the big picture of the area concerning used tools and open approaches with the goal to
      • Identify relevant technologies
      • Structure technologies and bring them into relation to each other
      • Identify technology gaps
      • Prepare a detailed outlook on a solution to be solved on a Hackfest
  • Testbed candidate 2 (data ingest), Thomas Reinhardt (Bosch)
  • ...

Workshop 2, Sept. 19, 2017 (Stuttgart, Germany) - Results

Strategy discussion results


- Certification organizations

- Universities

- Research institutes

- Standardization organizations like AUTOSAR can provide areas to watch out for

- These are in addition to already identified OEM, tier1, hi-tech, tool providers, silicon chip


- Need slide deck with a narrative to socialize inside of respective organizations

- Set up a public community under Eclipse management for contribution and preparation work prior to next workshop 23 October

- Weekly telecom to disseminate information – attendance voluntary based on availability

- Hosted communication at e.g. 3D Experience Forums by e.g. Dassault

Execution and milestones

- Further workshop to detail testbeds/incubators - October eclipsecon Europe

- Testbed/incubator execution (Hackathon/Hackfest) – November 2017

- Group composition for hackathon to be determined based on results of testbed/incubator layout

- Testbed/incubator completed by the end of 2017

- Announcement – venue dependent on testbed/incubator results and feasible timing (forums: CES, BCW, Software in Automobiles, Toulouse, Embedded World, WCX – sponsor is SAE International)

Forms of contribution by community members

- Manpower – e.g. programming capacity

- Monetary investment

- Material support - e.g. a car for demonstration purposes

Testbed/Incubator discussion results

1. Perception simulation and high quality rendering vs functional validation & simulation (FX to handle different simulation use cases)

- Simulation (formerly #11) – Workshop 1

- ROS in the loop

2. Driver to Driver communications

- Hybrid human -vs- autonomous driving behavior differenced – very hard problem

3. Car to X communications

4. Standardization

- Reference / canonical data set - Data Sharing across companies

- Share crash incident data across companies rapidly to accelerate safety resolution

- Open Scenarios - Common ways of defining scenarios

5. API standardization – common way of calling / creating API’s

6. Management & usage of big data

- Massive data ingest

7. Standardization interface for authority approvals based on defined data (independent of producer tool chain)

- There’s major value in driving agreement on how data is stored; can we drive agreement in which sensors are used and the format of the sensor data.

- This could benefit government agency that will test using the data to determine the safety of the vehicles

8. Heterogeneous data formats and data fusion

- Compatibility of measured data

- Visualization of data from different sources (lidar, video, measurements) could be very valuable

OpenADx testbed incubator discussion results.png


- It was agreed that we should concentrate on the top ranked topics #4, #6, #8.

- Proposed procedure is to set up a frequent call to discuss the topics and identify concrete tasks to be executed in "Hackfests“

- On the Unconference of the EclipseCon Europe on Oct. 23rd, the topics should be discussed further. Ideal result is to have them prepared for a "Hackfest".

- General agreement for participation in the concretization of the topics by XXXXXXX and XXXXX employees.

Workshop 1, Aug. 2, 2017 (Redmond, US) - Results

1. Gain points and pain points to address

Opportunities / gains

- Manage complexity / risk

- Reallocate portions of resource pool to more user relevant activities

- Commonality reduces risk

- Reduce cost in a non-automobile implementation area; the tool chain is outside of the vehicle

- AD development accelerator consists of known and certified components and services => ensure

Risks / pains

- What if this group of companies come together but is not actually able to complete the project

- Will this be fast enough to satisfy TTM needs of the OEMs

- How will sufficient safety levels be reached and assured

- Preserve independence: This initiative might actually preserve the second source needs OEM and Tier1 somewhat fearful of IT industry

2. Value proposition

- Reduced investment risk and cost reduction through shared development

- Improved capability to focus resources in more saleable areas

- Improved SW reliability and safety

- Standardization facilitates greater AD understanding and therefore greater acceptance in the political, legal and insurance communities

- Standardization promotes interchangeability @ OEM

3. Key success factors

=> Build momentum for the initiative

- Demonstrate that we can deliver; lofty vision is OK, but initial projects must be

=> Realistic / achievable

=> Clearly scoped

=> Measurable

- Start with a “coalition of the willing”

=> Not everyone will want to participate initially; reduce skepticism with results

- A common data pool to accelerate development

- Limit scope to non-differentiating factors

- Open APIs, Open framework and open collaboration => industry standard

=> Mix of multiple partners in each area… ”coopetition”

- Extensibility within the system to add modules without the OEM being required to open up all data access – that must remain a choice@OEM

Potential naming options

OpenADx Naming Options.jpg

Next steps

- Detail incubator procedure and timetable – Draft XX coordinate final version with XXXX

- Follow-up meeting incubator

=> Location Germany 18-19 September

=> XX, XXXX and proposed Hackfest participants

=> Ensure inclusion of OEM(s)

=> Include an additional Tier 1

- Hackfest Incubator 1, 2, 3

=> Location TBD

=> Target timing: mid-November


Pitch deck to be used inside of respective organizations

Back to the top