Skip to main content
Jump to: navigation, search

Difference between revisions of "OpenMobilityCharter"

(Technical Scope / Associated Projects)
(Participation Guidelines)
Line 98: Line 98:
 
* Regularly participate in Working Group meetings and provide timely feedback on Working Group documents.
 
* Regularly participate in Working Group meetings and provide timely feedback on Working Group documents.
 
* Provide ongoing marketing and community development support to the Eclipse OpenMobility community.
 
* Provide ongoing marketing and community development support to the Eclipse OpenMobility community.
 +
* ''the money alternative is missing''
 +
 +
* Each Steering Committee member has one vote.
  
 
==== Member Participants ====
 
==== Member Participants ====

Revision as of 07:06, 14 November 2017

Definitions

The following terms are used in this document:

  • Term...

Introduction

Mobility is a basic human need as well as a defining part of human development. It has always been a driver for innovation and technological advancements in a variety of domains and applications. Understanding and predicting mobility and traffic induced effects is a complex task. To master this task it is key to understand the interconnected world in which the mobility of persons and goods but also of information and data shapes global trade and work commutes the same way it gives rise to new business models such as on demand car sharing or in time food delivery. The complexity and variability of traffic phenomena make simulation an unique/effective tool for designing, analyzing and evaluating traffic systems.

Vision and Goals

WHY create an OpenMobility WG?

Mobility is a driving factor for modern societies. Different groups rely on different approaches, tools and paradigms on how mobility applications are developed. We think that there is a need to harmonize and standardize this process across vendors and researchers from academia. The objective of the OpenMobility Working Group is to develop, standardize and promote open source solutions and interfaces towards an open and modular mobility simulation framework.

WHAT does the OpenMobility WG do?

The OpenMobility Working Group is explicitly developing open source solutions to ensure vendor neutrality and openness for research and academia. It aims for supplying valid models which help to evaluate new mobility approaches before bringing them into action in a scientifically sound manner as well as providing an easily accessible infrastructure to model traffic scenarios.

WHO participates in the OpenMobility WG?

The OpenMobility WG is a collaboration of vendors from and around the automotive industries as well as research groups and individuals from academia.

How does the OpenMobility WG accomplish its goals?

By fostering and leveraging collaboration among members and ensuring the availability of the simulation framework as a platform, the OpenMobility Working Group lays the groundwork for the fulfillment of its mission. This framework not only includes the simulation of the movement of vehicles and people, but also covers its links to information transmission technologies and associated new business concepts, such as Mobility as a Service. At its core, the framework focuses on modeling and simulating the dynamics and interactions of all moving entities, such as cars, trains, bicycles, pedestrians, etc.

Purpose and Scope

The Open Mobility Working Group coordinates, influences and develops open source solutions with the following focus:

  • Microscopic and Mesoscopic traffic simulation including vehicle dynamics and interaction with the infrastructure
  • Car2X communication
  • Routing
  • Testbed for autonomous driving
  • Provide the environment to model many different modes of transport

Intended application domains for this framework are traffic management and logistics but also application testing and evaluation for car manufacturing and the automotive industry. Further target groups are consultants, public agencies, academia, and everyone with an interest in traffic and communication modelling.

The main purpose is to concentrate on the simulation and solution development for mobility problems on a city or regional level. While building interfaces between the tools developed in the group and additional tools such as car simulators or large scale traffic demand models is one of the core tasks, the group will not focus on implementing all models (such as submicroscopic or detailled demand models) themselves.

The group's aim is to deliver validated models which can be accepted as standard tools in academic as well as industry applications. To this end the members of the group will focus not only on tool development but also on teaching and disseminating their application as well as expanding and integrating the user base.

Technical Scope / Associated Projects

The OpenMobility Working group will work on the following topics and the associated projects:

  • Microsocopic Traffic Simulation (SUMO)
  • Vehicle-to-Vehicle and Vehicle-to-Infrastructure Communication
  • Simulator coupling
  • Interfacing to existing Advanced Driver Assistance Systems and Intelligent Transportation Systems solutions

Projects hosted by the Eclipse Foundation in the context of the OpenMobility 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 based on their merits. 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.

Governance

Applicable documents and Processes

In the event of any conflict between the terms set forth in the OpenMobility Working Group Charter and the Eclipse Foundation Bylaws, Membership Agreement, Eclipse Development Process, Eclipse Working Group Process, or any policies of the Eclipse Foundation, the terms of the Eclipse Foundation Bylaws, Membership Agreement, processes, or policies shall take precedence.

The OpenMobility Working Group will apply the Eclipse Foundation processes where applicable. In particular, the following processes shall be applied to the work of the WG itself:

  • Eclipse Working Group Process
  • Eclipse Development Process
  • Eclipse IP Process

Steering Committee Roles and Responsibilities

The Eclipse OpenMobility Working Group will have a Steering Committee to help guide the strategy and operation of the working group. The Steering Committee will make decisions based on a simple majority vote of the committee members.

The roles and responsibilities of the Steering Committee include:

  • Provide guidance and approval of the annual Eclipse OpenMobility Group strategy, positioning and roadmap.
  • Approve the technical architecture and composition of any Eclipse OpenMobility simulator/technology that is based on the overall roadmap.
  • Coordination and recruitment of resources to accelerate key project development and integration of the Eclipse OpenMobility roadmap.
  • Coordinate Eclipse OpenMobility Working Group membership recruitment
  • Approval of any Eclipse OpenMobility documents, include technical architectures, blueprints, white papers
  • Elect a chair of the Eclipse OpenMobility Working Group
  • Define the Eclipse OpenMobility working group budget and annual fees.

Participation Guidelines

Steering Committee Member

Steering committee members are required to:

  • Be a Strategic, Enterprise or Solutions member of the Eclipse Foundation.
  • Lead at least one Eclipse OpenMobility project and contribute at least XX FTE working on Eclipse OpenMobility projects or Eclipse OpenMobility Working Group activities. The activities can include
  1. committers working on Eclipse open source projects that support the OpenMobility roadmap,
  2. creation of roadmaps and technical documents (including, for example, architectures, blueprints and best practices) supporting the OpenMobility Working Group,
  3. evangelism and community development for the working group and
  4. other activities agreed to by the Steering committee.
  • MORE TO BE ADDED!
  • Regularly participate in Working Group meetings and provide timely feedback on Working Group documents.
  • Provide ongoing marketing and community development support to the Eclipse OpenMobility community.
  • the money alternative is missing
  • Each Steering Committee member has one vote.

Member Participants

Member participants are required to:

  • Be an Eclipse Foundation member at the Strategic, Enterprise or Solution level.
  • Regularly participate in the Working Group meetings.

Eclipse Foundation Associate Members may be invited by the Steering Committee to join and participate in the Working Group.

Services

Infrastructure

The OpenMobility Working Group uses the normal infrastructure provided to Eclipse projects, including, among others, mailing lists, forums, bug trackers, source code repositories, continuous integration servers, build servers, and web sites.

Community Building

The Eclipse Foundation will provide access to its network of developers to facilitate the community building and the dissemination of the OpenMobility innovations. The EF will use its communication channels such as its Newsletter, Twitter, or LinkedIn channels to promote key OpenMobility events and encourage its members to join and participate in the OpenMobility Working Group

Miscellaneous

Update of the charter

This charter should be updated by the Steering Committee, after a positive vote of 2/3 of the Steering Committee members.

Back to the top