Version v1.0. Revision history is at end of document.
Autonomous driving (AD) is an extremely complex challenge with a complex development process,
which is slowed at every turn by incompatibility between widely used development tools. The tools
we already use in and of themselves are very good, but they do not work seamlessly with one
another simply because they were never designed to work with each other.
This is an industry-wide issue. It slows us all down in the race to automated driving. It costs money and precious resources to reduce the problem to a manageable level. And the thing about it is that the tool chain itself is not something we can monetize.
All major stakeholders/users have issues associated with tool incompatibility, data conversion and lost time.
We lessen this problem by creating the leading automated driving ecosystem ➢ OpenADx
We leverage open collaboration and open source to
It is the goal of this working group (WG) to deliver
The working group will:
The OpenADx working group will coordinate the development of Eclipse Foundation projects on the following topics:
Projects hosted by the Eclipse Foundation in the context of the OpenADx working group apply the Eclipse development process and best practices of openness, transparency and meritocracy. As such, these projects are open to participation by developers or contributors. They can submit contributions to the project that will be considered for inclusion by the project committers. Committer status is acquired by contributors after election by existing committers as described in the Eclipse Development Process.
The OpenADx working group starts with an incubation period that runs through June 30, 2020. The goal of the incubation period is to
During the incubation period, only three membership classes and one governance body are defined (see “Membership”). Participant members and Committers of associated Eclipse Foundation projects are expected to actively engage in the development of this working group and the acquisition of new members. The participation fees for the working group will be waived during this period (0 € / USD 0 for all members).
The incubation period is concluded successfully if at least four Participant members have been acquired and a funding model for the group has been developed and agreed upon. From here on, the working group shall continue with an updated charter.
If the operation of this working group cannot be ensured on a sustainable basis, it will be terminated after the incubation period.
All Members must be parties to the Eclipse Foundation Membership Agreement, including the requirement set forth in Section 2.2 to follow the Bylaws and then-current policies of the Eclipse Foundation, including but not limited to the Intellectual Property and Anti-Trust Policies.
In the event of any conflict between the terms set forth in this Working Group's Charter and the Eclipse Foundation Bylaws, Membership Agreement, Eclipse Development Process, Eclipse Industry Working Group Process, or any policies of the Eclipse Foundation, the terms of the Eclipse Foundation Bylaws, Membership Agreement, process, or policy shall take precedence.
In order to participate in the OpenADx working group, an entity must be at least a Solution Member of the Eclipse Foundation, have executed the OpenADx Participation Agreement, and adhere to the requirements set forth in this Charter.
The OpenADx working group is open at any time to all new members who meet these conditions.
During the incubation period, there are three classes of OpenADx working group membership – Interested Parties, Participant Members and Committer. Each of these classes is described in detail below.
Interested Members are typically organizations that view an open toolchain as strategic to their organization. Interested Members are willing and allowed to work on and bring their ideas in this working group, but they have no voice in the decision process. Typical Interested Members include industry users of the technologies and results provided by the OpenADx working group.
Participant Members are typically organizations that view an open toolchain as strategic to their organization and are willing to invest significant resources to sustain and shape the activities of this working group. Typical Participant Members include industry users of the technologies and results provided by the OpenADx working group.
Committer Members are individuals who through a process of meritocracy defined by the Eclipse Development Process are able to contribute and commit code to the Eclipse Foundation projects included in the scope of this working group. Committers may be members by virtue of working for a member organization, or may choose to complete the membership process independently if they are not. For further explanation and details, see the “Eclipse Committer Membership” page.
The membership classes of the OpenADx WG are established to reflect the different interest situations of the members. The membership class has to be declared by the potential member in his OpenADx WG participation agreement. The membership class of each OpenADx WG member is checked once a year.
Driver Members are typically organizations that view the OpenADx activities as strategic to their
organization and are willing to invest significant resources to sustain and shape the activities
of this working group as well as maintain the scope of OpenADx.
Driver Members include industry users and strategic contributors related to the technologies and results provided by the OpenADx working group.
Driver members will lead the operation of the working group, support the OpenADx projects and will act as first contact of the working group.
Development Members are organizations that are interested to benefit from the OpenADx community. They will lead or participate in OpenADx projects and investigate the technical questions. They will propose and execute the OpenADx projects according to the processes defined by the OpenADx working group. Development members will invest efforts to the OpenADx projects as defined in the proposal.
User Members use the technologies and results provided by the OpenADx WG. They want to keep track
of the OpenADx development but do not want to influence in an essential way.
User Members are willed and allowed to work on and bring their ideas in this working group, but they have no voice in the decision process. Typical User Members include industry users of the technologies and results provided by the OpenADx working group. Most User Members operate testing processes as part of their core business.
Guests are organizations who have been invited for one year by the Steering Committee of OpenADx WG to participate in some aspects of the activities of the Working Group. Typical Guests include all stakeholders in automated driving and beyond, such as R&D partners, academic entities, legislators, consumer protection advocates, insurance companies, and potential future full-fledged members who want to have a closer look before deciding on their strategy. When Guests are invited to an OpenADx WG body for meetings, they have no right to vote. Invitations may be renewed by the Steering Committee. Guests are required to sign the participation agreement.
Guests need to be at least Eclipse Associate Members.
The Steering Committee will establish annual participation fees, and these fees will be reviewed and ratified by the Steering Committee on an annual basis. All participants in the working group will be informed of any changes in the participation fees, and this charter will be updated to reflect the established participation fees. The OpenADx Participation Agreement will stipulate that all members agree to pay the participation fees. The Membership Fee Structure shown below lists proposed annual participation fees for the first year beyond incubation, and once ratified by the Steering Committee, will come into effect beginning July 1, 2020.
In addition to annual participation fees, member organizations participating in OpenADx are expected to contribute employee service days to the benefit of the working group. Results for employee service days can be delivered as:
The corresponding packages or services have to be offered in advance to and accepted by the steering committee.
The Steering Committee shall establish an annual budget, and in conjunction with Eclipse Foundation staff, shall administer that budget on behalf of the working group.
All members are welcome to make voluntary donations of both additional funding and employee service days to the benefit of the working group.
All members of OpenADx agree to adhere to the Eclipse Bylaws and this charter, including to meet their financial and employee service day commitments. The Steering Committee is responsible for auditing the employee service day contributions of members, and will inform Eclipse Management Organization (EMO) of any member failing to meet its commitments.
This OpenADx working group is designed as:
In order to implement these principles, the “Steering Committee” as the sole governance body for the working group during the incubation phase has been defined.
In addition, a general meeting of the working group, open to all members, shall be held at least once annually.
Steering Committee members are required to:
The Steering Committee elects among its members a chairman who will represent the WG.
The following table lists: a) the annual Eclipse Foundation Solutions membership fees, shown here for convenience, and b) the OpenADx working group fees payable to the Eclipse Foundation Inc.
|Annual Corporate Revenue||Eclipse Solutions Membership||WG Fees Driver Member||WG Fees Development Member||WG Fees User Member|
|> $250 million||$ 20,000||$ 0||$ 0||$ 0|
|> $100 Million <= $250 million||$ 15,000||$ 0||$ 0||$ 0|
|> $50 million <= $100 million||$ 10,000||$ 0||$ 0||$ 0|
|> $10 million <= $50 million||$ 7,500||$ 0||$ 0||$ 0|
|< $10 million||$ 5,000||$ 0||$ 0||$ 0|
|< $1 million, < 10 employees||$ 1,500||$ 0||$ 0||$ 0|
Additionally, each member has to provide annual employee service days to the WG, measured in manpower units / money:
|Privilege||Driver Member||Development Member||User Member||Guests|
Charter Version History
Back to the top