Skip to main content
Jump to: navigation, search

Difference between revisions of "Open-Measured-Data-Management-WG"

m
(Events)
 
(73 intermediate revisions by 3 users not shown)
Line 1: Line 1:
<strong>The Open Measured Data Management Working Group wants to foster and support an open and innovative eco-system providing tools and systems, qualification kits and adapters for standardized and vendor independent management of measurement data in accordance with the [https://wiki.asam.net/display/STANDARDS/ASAM+ODS ASAM ODS] standard.</strong>
+
[[File:OpenMDMLogo.jpg|thumb|right]]
 +
The Open Measured Data Management Working Group leads the implementation of a vendor-neutral Open Source Software
 +
platform for the management of measured data.
 +
In compliance with the [https://wiki.asam.net/display/STANDARDS/ASAM+ODS ASAM ODS] standard, this
 +
platform enables an ecosystem that includes both
 +
automotive companies building inhouse applications and application vendors building commercial
 +
and open source solutions, tools and systems.
 +
Members of the working group include automotive
 +
OEMs as well as service providers and application
 +
vendors.
 +
The openMDM working group is coordinating the
 +
Eclipse mdmbl project, published under the business friendly Eclipse Public License 2.0 (EPL-2.0).
  
== Steering Committee (2017/2018)==
+
In summary, it implements an industry standard
 +
platform for tools and products for ODS compliant
 +
products and tool chains. <br>
 +
The platform is currently
 +
in use at the openMDM members Audi, BMW and
 +
Daimler, while Siemens and Müller-BBM are providing <br>
 +
products including the open platform.
 +
 
 +
= Welcome to OpenMDM =
 +
 
 +
== Steering Committee (2019/2020)==
  
 
'''Speaker of the Steering Committee''': N.N.
 
'''Speaker of the Steering Committee''': N.N.
  
Christian Krenner, [http://www.audi.com/index.html AUDI AG] on behalf of Volkswagen Group of America, Inc.
+
Ulrich Wierl, [http://www.audi.com/index.html AUDI AG] on behalf of Volkswagen Group of America, Inc.
  
 
Ulrich Bleicher, [http://bmw.com BMW Group]
 
Ulrich Bleicher, [http://bmw.com BMW Group]
Line 15: Line 36:
 
Gert Sablon, [http://www.siemens.com Siemens AG]
 
Gert Sablon, [http://www.siemens.com Siemens AG]
  
Sanjay Hande, [http://www.tatamotors.com/ Tata Motors Ltd.], representative of strategic users
+
Kartiki Deshpande, [http://www.tatamotors.com/ Tata Motors Ltd.], representative of strategic users
 
+
Holger Kremß, [https://www.itemis.com Itemis AG], elected representative of service providers
+
  
Hans-Dirk Walter, [http://www.canoo.com Canoo GmbH], elected representative of service providers
+
Hans-Dirk Walther, [https://karakun.com/ Karakun], elected representative of service providers
  
 
Dr. Ralf Nörenberg, [http://www.highqsoft.de/en/ HighQSoft GmbH], representative of application vendors
 
Dr. Ralf Nörenberg, [http://www.highqsoft.de/en/ HighQSoft GmbH], representative of application vendors
  
For details about the committee, see [[Open-Measured-Data-Management-WG/Steering_Committee]].
+
For details about the committee including meeting minutes, see [[Open-Measured-Data-Management-WG/Steering_Committee | Steering Committee]].
  
== Architecture Committee (2017/2018)==
+
== Architecture Committee (2019/2020)==
  
 
'''Chairman of the Architecture Committee''': Stefan Ebeling, BMW Group
 
'''Chairman of the Architecture Committee''': Stefan Ebeling, BMW Group
Line 31: Line 50:
 
Stefan Wartini, [http://www.muellerbbm-vas.de Müller-BBM VibroAkustik Systeme GmbH]
 
Stefan Wartini, [http://www.muellerbbm-vas.de Müller-BBM VibroAkustik Systeme GmbH]
  
Winfried Keim, [http://www.daimler.com Daimler AG]
+
Matthias Ebeling, [http://www.daimler.com Daimler AG]
  
 
Jan Blockx, [http://www.siemens.com SIEMENS AG]
 
Jan Blockx, [http://www.siemens.com SIEMENS AG]
Line 43: Line 62:
 
For details about the committee, see [https://wiki.eclipse.org/Open-Measured-Data-Management-WG/Architecture_Committee Open-Measured-Data-Management-WG/Architecture_Committee]
 
For details about the committee, see [https://wiki.eclipse.org/Open-Measured-Data-Management-WG/Architecture_Committee Open-Measured-Data-Management-WG/Architecture_Committee]
  
== Quality Committee (2017/2018)==
+
== Quality Committee ==
  
 
'''Speaker of the Quality Committee''': NN
 
'''Speaker of the Quality Committee''': NN
Line 56: Line 75:
 
! Company  !! Role
 
! Company  !! Role
 
|-  
 
|-  
| ASAM e.v
+
| ASAM e.V.
 
| Guest Member
 
| Guest Member
 +
|-
 +
| Atos (science+computing)
 +
| Service Provider
 
|-  
 
|-  
 
| AUDI AG on behalf of Volkswagen Group of America, Inc.  
 
| AUDI AG on behalf of Volkswagen Group of America, Inc.  
Line 64: Line 86:
 
| BMW Group
 
| BMW Group
 
| Driver Member
 
| Driver Member
|-
 
| Canoo Engineering AG
 
| Service Provider
 
 
|-  
 
|-  
 
| Daimler AG
 
| Daimler AG
 
| Driver Member
 
| Driver Member
|-
 
| Gigatronic  GmbH
 
| Service Provider
 
 
|-  
 
|-  
 
| HighQSoft GmbH
 
| HighQSoft GmbH
 
| Application Vendor
 
| Application Vendor
 
|-  
 
|-  
| itemis AG
+
| Karakun AG
 
| Service Provider
 
| Service Provider
|-  
+
|-
 
| Mueller-BBM VibroAkustik Systeme GmbH
 
| Mueller-BBM VibroAkustik Systeme GmbH
 
| Driver Member
 
| Driver Member
 
|-  
 
|-  
| Peak Solutions GmbH
+
| Peak Solution GmbH
 
| Service Provider
 
| Service Provider
 
|-  
 
|-  
Line 117: Line 133:
  
 
For more information, contact or subscribe to the [https://dev.eclipse.org/mailman/listinfo/open-measured-data-wg public WG mailing list].
 
For more information, contact or subscribe to the [https://dev.eclipse.org/mailman/listinfo/open-measured-data-wg public WG mailing list].
 
Members should also join the [https://dev.eclipse.org/mailman/listinfo/open-measured-data-wg-sc closed internal mailing list].
 
  
 
Detailed technical topics should be discussed in the developer mailing lists of the [[Open-Measured-Data-Management-WG#Related_Eclipse_Projects|corresponding projects]].
 
Detailed technical topics should be discussed in the developer mailing lists of the [[Open-Measured-Data-Management-WG#Related_Eclipse_Projects|corresponding projects]].
  
Access to [https://openmdm.atlassian.net/ JIRA]: Create a user (use the login button on the JIRA weppage) if you have not already one. Create a new ticket with your requests and assign it to jira.maintainer. The ticket will be processed by the administrators. All communication is done via the ticket, no extra email communication is necessary.
+
== Events ==
  
== Current Contributions ==
+
=== openMDM meets OpenADx:===
 +
online event: June 17, 2020, 2:00 PM – 5:00 PM CEST <br>
 +
We want to find out the collaboration potential between openMDM and OpenADx. <br>
  
[[Open-Measured-Data-Management-WG/UserAuthenticationAndRights|User Authentication & Rights]]
+
'''Slides:'''
 +
* [https://wiki.eclipse.org/images/c/c9/OpenMDM_meets_OpenADx_Agenda.pdf Agenda]
 +
* [https://wiki.eclipse.org/images/b/b4/200617_-_openMDM_meets_OpenADx_Andy.pdf OpenADx – xcelerate your Autonomous Driving development, Andy Riexinger]
 +
* [https://wiki.eclipse.org/images/0/0d/PresentationOpenMDM2020.pdf openMDM - Open Source Platform for implementing Test Data Management, Dr. Hans-Jörg Kremer, Peak Solution GmbH]
 +
* [https://wiki.eclipse.org/images/2/20/Labeling_MDM_presentation.pdf Data Labeling and Standards, Nicola Croce, deepen]
  
== Events, Activities and News ==
+
== Documents ==
  
=== December 2016 ===
+
=== General ===
  
Dec 13, 2016: Steering Committee Meeting at Mueller-BBM in Planegg
+
[https://www.eclipse.org/org/workinggroups/mdmwg_charter.php Working Group Charter]
  
=== September 2016 ===
+
[https://www.eclipse.org/org/workinggroups/wpga/openmdm_working_group_participation_agreement.pdf WG Participation Agreement]
  
On Sept. 27. SC-Meeting in Tuebingen.
+
[[Open-Measured-Data-Management-WG/Glossary|Glossary (outdated)]]
  
[[Open-Measured-Data-Management-WG/FormerEvents|Former Events]]
+
=== Publications ===
 
+
== Past News and Articles ==
+
 
+
This content has been moved to [https://www.openmdm.org openmdm.org]
+
 
+
== Relevant Conferences ==
+
 
+
== Publications ==
+
  
 
Press releases about the founding of the openMDM Working Group:
 
Press releases about the founding of the openMDM Working Group:
  
[http://www.peak-vmm.de/english/media-information/media-information/eclipse-openmdmr-working-group-established.html Eclipse openMDM® Working Group established]
+
[https://www.peak-solution.de/en/professional-article/media-information/vmm-eclipse-openmdm-working-group-established.html Eclipse openMDM® Working Group established]
  
 
[http://mmilinkov.wordpress.com/2014/07/29/introducing-openmdm/ Leading Automotive Companies to Collaborate at Eclipse: Introducing openMDM]
 
[http://mmilinkov.wordpress.com/2014/07/29/introducing-openmdm/ Leading Automotive Companies to Collaborate at Eclipse: Introducing openMDM]
Line 160: Line 172:
 
[http://jaxenter.de/news/audi-bmw-daimler-openmdm-eclipse-foundation-175222 Audi, BMW und Daimler unter dem Dach der Eclipse Foundation vereint]
 
[http://jaxenter.de/news/audi-bmw-daimler-openmdm-eclipse-foundation-175222 Audi, BMW und Daimler unter dem Dach der Eclipse Foundation vereint]
  
[https://www.audi-mediaservices.com/publish/ms/content/de/public/pressemitteilungen/2014/07/25/audi_ag__bmw_group.html Audi Media Services: AUDI AG, BMW Group und Daimler AG treiben Open Source Messdatenmanagement voran]
+
[https://audimediacenter-a.akamaihd.net/system/production/uploaded_files/1512/file/dd4653ddaaf4e1f26f28f7ac9bc606664e554897/PI_Gruendung_Eclipse_openMDM_Working_Group_140725_3.pdf?1484227412 Audi Media Services: AUDI AG, BMW Group und Daimler AG treiben Open Source Messdatenmanagement voran]
  
== Documents ==
+
=== Guidelines ===  
  
[https://www.eclipse.org/org/workinggroups/mdmwg_charter.php Working Group Charter]
+
[https://wiki.eclipse.org/images/d/df/OpenMDM-Guidelines_for_external_contributions_V01-0.pdf Guidelines for external contributions, Version 1.2, February 2020, approved by the Architecture Committee]
  
[https://www.eclipse.org/org/workinggroups/IWG_Participation_Agreement.pdf WG Participation Agreement]
+
[https://wiki.eclipse.org/images/5/50/OpenMDM_IP_management_and_Software_Licensing.pdf Introduction to the Eclipse IP managment processes for the openMDM EWG]
 
+
[http://git.eclipse.org/c/mdmweb/org.eclipse.mdmweb.architecture.git/ openMDM(R) 5 architecture definition]
+
  
 
[https://openmdm.atlassian.net/secure/attachment/21600/openmdm%20ewg-emo%20decision%20procedure%20v10.docx Eclipse Working Group SC decision process for work package assignment]
 
[https://openmdm.atlassian.net/secure/attachment/21600/openmdm%20ewg-emo%20decision%20procedure%20v10.docx Eclipse Working Group SC decision process for work package assignment]
  
[[Open-Measured-Data-Management-WG/Glossary|Glossary]]
+
=== Past News and Articles & Conferences ===
  
[https://wiki.eclipse.org/images/d/df/OpenMDM-Guidelines_for_external_contributions_V01-0.pdf Guidelines for external contributions, Version 1.0, May 2018, defined by the Architecture Committee]
+
This content has been moved to [https://www.openmdm.org openmdm.org]
 +
 
 +
=== Flyer ===
 +
[https://wiki.eclipse.org/images/4/4a/Open_MDM_Flyer_v1-0.pdf openMDM Flyer, ASAM International Conference, Dec 2019]
 +
 
 +
[https://wiki.eclipse.org/images/7/71/AutomotiveFlyer-v1-1.pdf Automotive Working Group Flyer, Oct 2019]
  
 
== Related Eclipse Projects ==
 
== Related Eclipse Projects ==
  
[https://projects.eclipse.org/projects/technology.mdmbl MDM|BL]<br>
+
=== [https://projects.eclipse.org/projects/technology.mdmbl MDM|BL] ===
The MDM|BL project will hold the "business layer" of the openMDM(R) toolkit. This includes the definition of the openMDM(R) business object model, the corresponding ASAM ODS application model in conjunction with the rules for its generic extension due to the openMDM(R) business object model, the definition of the high level interfaces and the so called openMDM(R) API.
+
  
'''Documentation''':
+
''' NEW - Try the [http://demo.openmdm.org/ openMDM Application Demo online] '''
* [https://wiki.eclipse.org/images/e/e0/GettingStarted_mdmbl.pdf Getting Started Guide for Developers]
+
* [https://wiki.eclipse.org/images/8/8a/InstallationGuide_openMDM5_Application.pdf Installation Guide for a Demo Environment]
+
  
[https://projects.eclipse.org/projects/technology.mdmweb MDM@WEB]<br>
+
The Eclipse mdmbl project implements a server
The MDM@WEB project covers components which are required to build a web client to work with data according to the ASAM ODS standard for reading and reporting purposes. It facilitates the interaction with servers following the ASAM ODS standard, file based exchange of (meta-)data, and provides a graphical user interface for browsing and handling the available data.
+
platform that through its scalable backend architecture can serve many ODS compliant servers
 +
in parallel for data ingest, data exploration, test
 +
management, user and access management and
 +
more. It exposes a RESTful interface for clients,
 +
hiding much of the complexity of the ASAM ODS
 +
interface specification.
 +
Security mechanisms at the data and functional
 +
level protect the stored information against unauthorized access.
  
'''Note''': As per recommendation of the openMDM SC this project is not longer active and archived [https://openmdm.atlassian.net/browse/ORGA-216]
+
The following commercial ODS servers have been
 +
tested for use with the platform:
 +
* Peak ODS Server from Peak Solution GmbH
 +
* Avalon from HighQSoft GmbH
 +
 
 +
 
 +
Through its open adapter interface, proprietary
 +
non-ODS compliant storage systems can be connected, for example, PAK Cloud from Müller-BBM.
 +
 
 +
With major versions V5.0 released in Q4/2018, V5.1 released in Q1/2020, the
 +
team is working towards V5.2 to be released Q1/2021.
 +
 
 +
For more information, contact or subscribe to the [https://accounts.eclipse.org/mailing-list/mdmbl-dev public dev mailing list].
 +
 
 +
For ongoing activities see the [https://projects.eclipse.org/projects/technology.mdmbl/releases/5.2.0/plan release plan], requirements, issues and bugs are tracked [https://bugs.eclipse.org/bugs/buglist.cgi?quicksearch=mdmbl here].
 +
 
 +
'''Documentation''':
 +
* [https://download.eclipse.org/mdmbl/nightly_master/5.2.0M2/GettingStarted_mdmbl.pdf Getting Started Guide]
 +
* [https://projects.eclipse.org/projects/technology.mdmbl/downloads Documentation for previous versions]
  
Documentation for previous version can be found [https://projects.eclipse.org/projects/technology.mdmbl/downloads here].
+
=== [https://projects.eclipse.org/projects/technology.mdmweb MDM@WEB] - inactive and archived ===
  
 
== Resources ==
 
== Resources ==
Line 196: Line 233:
 
[http://openmdm.org openMDM(R) public web site]  
 
[http://openmdm.org openMDM(R) public web site]  
  
[https://openmdm.atlassian.net/ openMDM(R) EWG issue tracking]
+
[https://bugs.eclipse.org/bugs/buglist.cgi?quicksearch=mdmbl openMDM(R) EWG issue tracking]
  
 
[https://wiki.eclipse.org/File:OpenMDM_Office_Templates.zip openMDM(R) EWG document and presentation templates]
 
[https://wiki.eclipse.org/File:OpenMDM_Office_Templates.zip openMDM(R) EWG document and presentation templates]

Latest revision as of 04:00, 6 July 2020

OpenMDMLogo.jpg

The Open Measured Data Management Working Group leads the implementation of a vendor-neutral Open Source Software platform for the management of measured data. In compliance with the ASAM ODS standard, this platform enables an ecosystem that includes both automotive companies building inhouse applications and application vendors building commercial and open source solutions, tools and systems. Members of the working group include automotive OEMs as well as service providers and application vendors. The openMDM working group is coordinating the Eclipse mdmbl project, published under the business friendly Eclipse Public License 2.0 (EPL-2.0).

In summary, it implements an industry standard platform for tools and products for ODS compliant products and tool chains.
The platform is currently in use at the openMDM members Audi, BMW and Daimler, while Siemens and Müller-BBM are providing
products including the open platform.

Welcome to OpenMDM

Steering Committee (2019/2020)

Speaker of the Steering Committee: N.N.

Ulrich Wierl, AUDI AG on behalf of Volkswagen Group of America, Inc.

Ulrich Bleicher, BMW Group

Matthias Ebeling, Daimler AG

Josef Hobelsberger, Müller-BBM VibroAkustik Systeme GmbH

Gert Sablon, Siemens AG

Kartiki Deshpande, Tata Motors Ltd., representative of strategic users

Hans-Dirk Walther, Karakun, elected representative of service providers

Dr. Ralf Nörenberg, HighQSoft GmbH, representative of application vendors

For details about the committee including meeting minutes, see  Steering Committee.

Architecture Committee (2019/2020)

Chairman of the Architecture Committee: Stefan Ebeling, BMW Group

Stefan Wartini, Müller-BBM VibroAkustik Systeme GmbH

Matthias Ebeling, Daimler AG

Jan Blockx, SIEMENS AG

Stefan Ebeling, BMW Group

NN AUDI AG on behalf of Volkswagen Group of America, Inc.

Angelika Wittek MDM|BL project lead

For details about the committee, see Open-Measured-Data-Management-WG/Architecture_Committee

Quality Committee

Speaker of the Quality Committee: NN

Activities and tasks of the Quality Committee have been transferred to the Architecture Committee. The Quality Committee may be reinstated at some point in the future.

For details about the committee, see Open-Measured-Data-Management-WG/Quality_Committee

Current Members

Company Role
ASAM e.V. Guest Member
Atos (science+computing) Service Provider
AUDI AG on behalf of Volkswagen Group of America, Inc. Driver Member
BMW Group Driver Member
Daimler AG Driver Member
HighQSoft GmbH Application Vendor
Karakun AG Service Provider
Mueller-BBM VibroAkustik Systeme GmbH Driver Member
Peak Solution GmbH Service Provider
Siemens AG Driver Member
Tata Motors Ltd. User Member

Founding Members

The charter has been approved by the executive director of the Eclipse Foundation, Mike Milinkovich, on July 11th, 2014. The Working Group has been created.

AUDI AG, on behalf of Volkswagen Group of America, Inc., Driver Member

BMW Group, Driver Member

Daimler AG, Driver Member

Canoo Engineering AG, Service Provider

Gigatronik, Service Provider

HighQSoft GmbH, Application Vendor

Peak Solution GmbH, Service Provider

science + computing ag, Service Provider

Organization and Contact

For more information, contact or subscribe to the public WG mailing list.

Detailed technical topics should be discussed in the developer mailing lists of the corresponding projects.

Events

openMDM meets OpenADx:

online event: June 17, 2020, 2:00 PM – 5:00 PM CEST
We want to find out the collaboration potential between openMDM and OpenADx.

Slides:

Documents

General

Working Group Charter

WG Participation Agreement

Glossary (outdated)

Publications

Press releases about the founding of the openMDM Working Group:

Eclipse openMDM® Working Group established

Leading Automotive Companies to Collaborate at Eclipse: Introducing openMDM

openMDM Working Group gegründet

Open-MDM Working Group gegründet: Audi, BMW und Daimler verwalten Messdaten gemeinsam

Audi, BMW und Daimler unter dem Dach der Eclipse Foundation vereint

Audi Media Services: AUDI AG, BMW Group und Daimler AG treiben Open Source Messdatenmanagement voran

Guidelines

Guidelines for external contributions, Version 1.2, February 2020, approved by the Architecture Committee

Introduction to the Eclipse IP managment processes for the openMDM EWG

Eclipse Working Group SC decision process for work package assignment

Past News and Articles & Conferences

This content has been moved to openmdm.org

Flyer

openMDM Flyer, ASAM International Conference, Dec 2019

Automotive Working Group Flyer, Oct 2019

Related Eclipse Projects

MDM|BL

NEW - Try the openMDM Application Demo online

The Eclipse mdmbl project implements a server platform that through its scalable backend architecture can serve many ODS compliant servers in parallel for data ingest, data exploration, test management, user and access management and more. It exposes a RESTful interface for clients, hiding much of the complexity of the ASAM ODS interface specification. Security mechanisms at the data and functional level protect the stored information against unauthorized access.

The following commercial ODS servers have been tested for use with the platform:

  • Peak ODS Server from Peak Solution GmbH
  • Avalon from HighQSoft GmbH


Through its open adapter interface, proprietary non-ODS compliant storage systems can be connected, for example, PAK Cloud from Müller-BBM.

With major versions V5.0 released in Q4/2018, V5.1 released in Q1/2020, the team is working towards V5.2 to be released Q1/2021.

For more information, contact or subscribe to the public dev mailing list.

For ongoing activities see the release plan, requirements, issues and bugs are tracked here.

Documentation:

MDM@WEB - inactive and archived

Resources

openMDM(R) public web site

openMDM(R) EWG issue tracking

openMDM(R) EWG document and presentation templates

openMDM(R) Logo package

External Links

ASAM e.V. web site

Back to the top