Unverified Commit 356bd014 authored by Yi (Flora) Liu's avatar Yi (Flora) Liu Committed by GitHub
Browse files

initial trial on homepage (#2)



* initial trial on homepage
Signed-off-by: Yi Liu's avatarYi Liu <yi.liu@eclipse-foundation.org>

* update jumbotron, members, news and some styling
Signed-off-by: Yi Liu's avatarYi Liu <yi.liu@eclipse-foundation.org>

* remove cookies.js
Signed-off-by: Yi Liu's avatarYi Liu <yi.liu@eclipse-foundation.org>

* remove unnecessary files and customs, adjust jumbotron, add events list, news and members page
Signed-off-by: Yi Liu's avatarYi Liu <yi.liu@eclipse-foundation.org>

* use template in node module and drop custom events shortcodes
Signed-off-by: Yi Liu's avatarYi Liu <yi.liu@eclipse-foundation.org>

* add featured story and subpages
Signed-off-by: Yi Liu's avatarYi Liu <yi.liu@eclipse-foundation.org>

* change jumbotron button to blue
Signed-off-by: Yi Liu's avatarYi Liu <yi.liu@eclipse-foundation.org>

* some updates according to the comments
Signed-off-by: Yi Liu's avatarYi Liu <yi.liu@eclipse-foundation.org>

* better align of members
Signed-off-by: Yi Liu's avatarYi Liu <yi.liu@eclipse-foundation.org>
parent 69dd6b18
......@@ -23,7 +23,10 @@ pluralizeListTitles = false
# logo_width = ""
# header_left_classes = ""
# main_menu_wrapper_classes = ""
featured_content_publish_target = "openmdm"
featured_content_publish_target = "openmdm"
call_for_action_text = "Download"
call_for_action_url = "//www.eclipse.org/downloads/"
call_for_action_icon = "fa-download"
[taxonomies]
category = "categories"
......@@ -46,4 +49,127 @@ featured_content_publish_target = "openmdm"
[blackfriday]
plainIDAnchors = true
hrefTargetBlank = true
\ No newline at end of file
hrefTargetBlank = true
[[menu.main]]
name = "Overview"
url = "/overview"
weight = 1
[[menu.main]]
name = "Technology"
url = "/technology"
weight = 2
[[menu.main]]
name = "Working Groups"
url = "/working-groups"
weight = 3
[[menu.main]]
name = "Members"
url = "/members"
weight = 4
[[menu.main]]
name = "News"
url = "/news"
weight = 5
[[menu.main]]
name = "Contact"
url = "/contact"
weight = 6
# Overview sub-menu
[[menu.main]]
name = "How it works"
url = "/overview/how-does-it-work"
parent = "Overview"
weight = 1
[[menu.main]]
name = "What is it"
url = "/overview/about-openmdm"
parent = "Overview"
weight = 2
[[menu.main]]
name = "Why choose"
url = "/overview/why-choose"
parent = "Overview"
weight = 3
[[menu.main]]
name = "History"
url = "/overview/history"
parent = "Overview"
weight = 4
[[menu.main]]
name = "ASAM ODS"
url = "/overview/asam-ods"
parent = "Overview"
weight = 5
# Technology sub-menu
[[menu.main]]
name = "Architecture"
url = "/technology/architecture"
parent = "Technology"
weight = 1
[[menu.main]]
name = "Interfaces"
url = "/technology/interfaces"
parent = "Technology"
weight = 2
[[menu.main]]
name = "Principles"
url = "/technology/principles"
parent = "Technology"
weight = 3
[[menu.main]]
name = "Related Eclipse Projects"
url = "/technology/related-eclipse-projects"
parent = "Technology"
weight = 4
[[menu.main]]
name = "Specifications"
url = "/technology/specifications"
parent = "Technology"
weight = 5
# Working Groups sub-menu
[[menu.main]]
name = "Scope"
url = "/working-groups/scope"
parent = "Working Groups"
weight = 1
[[menu.main]]
name = "Collaboration"
url = "/working-groups/collaboration"
parent = "Working Groups"
weight = 2
[[menu.main]]
name = "Governance"
url = "/working-groups/governance"
parent = "Working Groups"
weight = 3
[[menu.main]]
name = "Membership"
url = "/working-groups/membership"
parent = "Working Groups"
weight = 4
[[menu.main]]
name = "Participation"
url = "/working-groups/participation"
parent = "Working Groups"
weight = 5
\ No newline at end of file
---
title: "OpenMDM - Measured Data Management"
seo_title: "OpenMDM - Measured Data Management"
headline: "OpenMDM - Measured Data Management"
tagline: "OpenMDM - Measured Data Management"
headline: "Plan. Measure. Share."
tagline: "And simplify your measured data management."
jumbotron_tagline_class: "col-sm-18"
description: "openMDM® 5 is a kit of components and concepts, which can be used to compose applications for measured data management systems. The development of components and concepts is driven by the openMDM® Eclipse Working Group. All components and concepts are published under the Eclipse Public License."
date: 2020-09-08T11:00:00-04:00
layout: "single"
hide_breadcrumb: true
---
\ No newline at end of file
hide_sidebar: true
hide_page_title: true
show_featured_story: true
container: "container-fluid"
links: [[href: "/overview/how-does-it-work", text: "Plan. Measure. Share."], [href: "https://wiki.eclipse.org/Open-Measured-Data-Management-WG#Steering_Committee", text: "Learn More"]]
---
{{< grid/section-container >}}
{{< grid/div class="col-sm-15 margin-top-30" isMarkdown="false" >}}
{{< newsroom/news
title="News"
titleClass="heading-line text-center"
id="news-list-container"
publishTarget="openmdm"
count="5"
templateId="news-no-mh"
templatePath="node_modules/eclipsefdn-hugo-solstice-theme/js/templates/news-no-mh.mustache"
includeList="true" >}}
{{</ grid/div >}}
{{< grid/div class="col-sm-8 col-sm-offset-1 margin-top-30" isMarkdown="false" >}}
{{< newsroom/events
title="Events"
titleClass="heading-line text-center"
containerClass="news-items event-container"
id="events-list-container"
publishTarget="openmdm"
count="5"
templateId="event-list-format"
templatePath="node_modules/eclipsefdn-hugo-solstice-theme/js/templates/event-list-format.mustache"
includeList="true" >}}
{{</ grid/div >}}
{{</ grid/section-container >}}
{{< home-members >}}
\ No newline at end of file
---
title: "Contact"
date: 2020-09-08T11:00:00-04:00
hide_sidebar: true
seo_title: "Contact"
keywords: ["openmdm", "Contact"]
---
If you want to track the activities of the openMDM® Working Group, please sign up to the openMDM Mailing List.
For more information on the openMDM® Working Group or the openMDM® or the ongoing conversations, please visit our wiki.
**For the Eclipse Foundation:**
Ralph Mueller
Managing Director
Office: +49 6251 8606413
Mail: ralph.mueller@eclipse.org
\ No newline at end of file
---
title: Members
date: 2019-02-21
publishdate: 2019-02-21
---
{{< page-members >}}
\ No newline at end of file
---
title: News
date: 2019-02-21
publishdate: 2019-02-21
---
{{< newsroom/news
id="news-list-container"
publishTarget="openmdm"
count="10"
templateId="news-no-mh"
templatePath="node_modules/eclipsefdn-hugo-solstice-theme/js/templates/news-no-mh.mustache"
paginate="true" >}}
\ No newline at end of file
---
title: "Overview"
date: 2020-09-08T11:00:00-04:00
---
\ No newline at end of file
---
title: "What is it?"
date: 2020-09-08T11:00:00-04:00
hide_sidebar: true
seo_title: "What is it"
keywords: ["openmdm", "what is it"]
---
openMDM® 5 is a kit of components and concepts, which can be used to compose applications for measured data management systems. The development of components and concepts is driven by the openMDM® Eclipse Working Group. All components and concepts are published under the Eclipse Public License.
{{< figure src="/overview/images/about-openmdm.jpg" alt="about openmdm" >}}
&nbsp;
Based on open standards and open interfaces, the key features of openMDM® 5 include high reusability, flexible expandability and universal usability.
Using the openMDM® 5 building block, data management systems, differing in form and function, can be configured to offer a professional management of measurement data, evaluation results and their descriptions (metadata). New systems can be constructed from existing openMDM® blocks.
openMDM® 5 is able to describe measurement data with full syntax and completely semantically. This is made possible by employing ASAM ODS to standardize data storage. This creates the potential to merge and compare measurement data from different contexts. Data can be exchanged between all ODS-compatible applications without the need for conversion. Furthermore, ASAM ODS fulfils the requirements for an archiving format: You will still be able to interpret ODS data in 30 years’ time!
All this reduce your costs for the implementation of sophisticated measurement data management systems.
\ No newline at end of file
---
title: "ASAM ODS"
date: 2020-09-08T11:00:00-04:00
hide_sidebar: true
seo_title: "ASAM ODS"
keywords: ["openmdm", "ASAM ODS"]
---
ASAM (Association for Standardisation of Automation and Measuring Systems) is a worldwide organization that standardizes data models and interfaces for measurement, simulation and evaluation systems. One of its most important standards is ODS (Open Data Services), that has proven itself for over a decade as a reliable basis for the management of test and simulation data. Today the standard is used by a large number of well-known companies all over the world.
In contrast to proprietary solutions, the use of ASAM ODS has some important advantages:
- The possibility to store every boundary conditions of a test (= descriptive information) together with measured data and measurement results in a flexible way, allows you to find the test data very fast, interpret them clearly and compare them long term.
- The standardized access to test data ensures maximum transparency regarding the availability and provision of test data throughout test facilities, departmental and site boundaries.
- Based on the vendor-neutral data exchange format ATFX it is very easy to transfer measurement data together with its descriptive information between different measurement and analysis systems - without expensive conversion applications.
The standard allows to define subject-specific data models (= application models) for the administration of tests in a flexible way. Due to that many different applications can be covered. Examples of application areas are Noise Vibration Harshness (NVH), vehicle safety, engine development or driving tests.
In view of increasing legal requirements relating to proof obligation and product liability, many companies use the standard of ASAM ODS also for long-term archiving of test data. In this way it is ensured that important information can be specifically found and interpreted correctly even after many years, regardless of individual persons and the software products of specific manufacturers
Here you can find more information about ASAM and the ODS standard:
- [www.ASAM.net](https://www.ASAM.net)
- [ASAM ODS Documentation](https://wiki.asam.net/display/STANDARDS/ASAM+ODS)
---
title: "History"
date: 2020-09-08T11:00:00-04:00
hide_sidebar: true
seo_title: "History"
keywords: ["openmdm", "history"]
---
In 1999 openMDM® originated as an idea for a reusable systems building block in multi-year planning and implementation projects for measurement data management systems in the Technical Development Department of AUDI AG.
From 2008 openMDM® was published by Audi as open source. From then on large vehicle manufacturers and suppliers such as Bosch, BMW, DAF, Daimler and FEV joined the open MDM community as active users and started in collaboration with different tool vendors and service provides their own openMDM® projects.
Since 2014 the establishment of the openMDM® Eclipse Working Group created a new organizational framework which makes it possible to push improvements and the international distribution of openMDM® more intensively.
{{< figure src="/overview/images/history.jpg" alt="history of openmdm" >}}
\ No newline at end of file
---
title: "How it works"
date: 2020-09-08T11:00:00-04:00
hide_sidebar: true
seo_title: "How it works"
keywords: ["openmdm", "how does it work"]
---
## User components
The user components of openMDM® support the user in carrying out different steps in the measurement process and allow the standardization and automation of repetitive workflows. Alongside the storage of the measurement data, the recording of descriptive data (metadata) is a central aspect in each process step. Metadata are important for the usability of any data management system since they are used for navigation, exploration, searches and for the ability to compare the measurement data.
The diagram illustrates the openMDM® standard process.
{{< figure src="/overview/images/how-does-it-work.jpg" alt="openMDM standard process" >}}
&nbsp;
Measurement systems and analysis tools from different vendors can be integrated into the workflow in a flexible way via open interfaces. Some process steps generate business objects which are intended for the user to see. These can include test orders, test results, reports, evaluations or references to data objects located in the ODS storage.
## Administration components
The administration components of openMDM® allow that applications can be easily tailored and adapted to specific use cases. The following topics can be administrated by selected users:
Data structures in which all descriptive information of a test (metadata) can be unambiguously stored. These include information describing the context of a test (e.g. unit under test, test equipment and test set up) as well as information describing the measurement result (e.g. measured quantities, units and channels).
Templates for the description of test procedures.
Specific application components to support the user in the test description and commissioning or automatic processing of data objects (e.g. automatic generation of test and test step names, transferring data from external systems, execution of actions when entering data and commissioning tests or mapping of attributes for assignment of measured data).
User roles, groups and permissions to ensure the confidentiality of test data.
Those tasks do not require ASAM ODS or database expert knowledge.
\ No newline at end of file
---
title: "Why Choose?"
date: 2020-09-08T11:00:00-04:00
hide_sidebar: true
seo_title: "Why choose"
keywords: ["openmdm", "why choose"]
---
You have been storing your measurement data for a long time in different, more or less proprietary and department specific data storage solutions. Now you find that you’re in one of the following situations:
**You are no longer able to assign your measurement data, you can’t find them now, or you don’t know where to look for them.**
Using openMDM® you can document your measurement data in your own terminology. You can ascribe descriptors, standardize terms and classify information. openMDM® automatically adapts to navigation and searches.
**You want to compare measurement results which were generated with different tools (test equipment, software) or under different conditions**
openMDM® guarantees comparability by using standardised and professionally described data storage. openMDM® processes descriptive content in the data and is thereby able to support the selection of comparison criteria, or reduce compatibility problems.
**You want to evaluate your measurement data with a new method which is available from another manufacturer**
openMDM® offers universal and stable standardisation and an interface concept that is open and independent of manufacturer.
**You want to transmit measurement data to a colleague or perhaps a partner organisation for further processing.**
openMDM® supports the storage and transmission of complete and fully specified information. Conversion problems do not arise and data are not lost.
**You want to reduce specific parts of your database.**
The openMDM® mechanics for classifying, segregating by type and describing information can also be used to manage life cycle processes.
**You have to demonstrate adherence to guidelines (such as product liability, diligence, security or data protection).**
openMDM® is able to control typical activities in the data life cycle (issuing and withdrawal of access rights, deletion, archiving). Data processing steps can be documented. By linking into company-wide authentication procedures, personal access right at the server level can be guaranteed. If necessary, additional encryption procedures can be configured.
**Your team has planned various tests and you want to be kept informed on how the work is progressing.**
openMDM® will provide continuous updates to give a clear overview at any given time, including the possibility of specifying workflows.
**You have planned a test and specified all boundary conditions, but in performing the test you can comply with only some of these conditions.**
Since openMDM® is able to keep a record of the planning of a test separate from its execution, you can reassess the relevance of test results with the benefit of hindsight.
**You want to distribute your measurement data between different sites without significant losses in performance**
openMDM® is based on the secure, central management of databases in a central physical storage facility. Databases can be stored in the background.
\ No newline at end of file
---
title: "Architecture"
date: 2020-09-08T11:00:00-04:00
hide_sidebar: true
seo_title: "Architecture"
keywords: ["openmdm", "architecture"]
---
openMDM® applications consist of a collection of components that can be distributed on different computers within a network. The communication between these components is done via defined interfaces.
Each component can be assigned exactly to one logical layer of the openMDM® architecture. The diagram provides an overview.
**ODS Services**
This layer contains the basic features and specifications of the ODS standard. The functions are provided by a ODS server via OO API.
**Application Model**
The application model is an openMDM®-specific implementation of the abstract ODS base model. It specifies the business objects that can be stored persistently in openMDM®. Although a large part of the generic constructs of ODS base model were dissolved, the storage structures for descriptive information (metadata) are designed to be very general and flexible. This layer can be extended with modular additions. In order to make the expansion of the application model accessible, an extension of the openMDM® API is required.
**Business Objects and Rules**
In order to highlight the particular importance of the openMDM® API, it is assigned to a separate layer. Any access to ODS is done via the openMDM® API. It defines the business objects (e.g. MeaResult) and other business rules of openMDM®. It is described in IDL and be used by overlying building blocks. If the application model is expanded, it must be a building block in this layer, which implements the access to the extension of the model.
**Extended Business Services**
This layer contains components which expand the openMDM® API by specific business objects (e.g. openMDM Entry) and functions (e.g. openMDM Syslog). They use the openMDM® API and are remote accessible for other blocks via their IDL interface. The layer can be extended to provide additional business objects, functions and rules.
**Platform interfaces**
This layer contains the interfaces for platform-specific runtime environments. For the current reference implementations this are those of the Java VM (e.g. I/O API) and OSGi Containers (e.g. OSGi EventAdmin).
**Non-UI interfaces**
Platform-specific interfaces that are not part of the user interface belong to this layer
**UI interfaces**
Interfaces that belong to the user interface and serve the presentation of information (e.g. the composition of different views) are part of this layer.
\ No newline at end of file
---
title: "Interfaces"
date: 2020-09-08T11:00:00-04:00
hide_sidebar: true
seo_title: "Interfaces"
keywords: ["openmdm", "interfaces"]
---
+ Programming interfaces on complete business model
+ Open documentation and version structuring of the interfaces in CORBA-IDL
+ Connection to external systems via standardised attribute mapping and a standard component
+ Expandability by adding own in-house components
+ Connection into company-wide authentication system (single sign-on)
+ List of coupled applications:
* Matlab (Mathworks)
* Famos (IMC)
* Diadem (National Instruments)
* Artemis (Head Acoustics)
* Head-Recorder (Head Acoustics)
* Engineering Data Portal (Müller-BBM VibroAkustik Systeme)
* PAK (Müller-BBM VibroAkustik Systeme)
* TestLab (LMS)
* TecWare (LMS)
* ...and many others
+ Importer/Exporter:
* Order interface (MDM-XML)
* Excel (MS)
* RPC II (MTS)
* ADTF (AEV/Electrobit)
* MDF3 (Vector Informatik)
* ATFX (ASAM)
* HDF (Head Acoustics)
* ATSC16/32 (Aditech)
* ...and many others
\ No newline at end of file
---
title: "Principles"
date: 2020-09-08T11:00:00-04:00
hide_sidebar: true
seo_title: "Principles"
keywords: ["openmdm", "principles"]
---
The openMDM® Industry Working Group focuses on processes, methods for standardization, data formats, techniques, frameworks and tools to fulfill its goals and vision, including:
* Providing and establishing methods and best practices for standardized and vendor- independent measured data management on the base of the ASAM ODS standard
* Maintenance of a reference process which serves for the positioning and classification of software components to support the reuse of software components
* Development and maintenance of a standardized, generic business object model represented by an ASAM ODS application model and corresponding interface definitions
* Providing a set of industry-friendly open source software components within a well defined framework
* Providing collaborative means to make open innovation easier
* Operating dedicated software repositories, build chains, test facilities, etc.
* Managing the quality and maturity of tools and software components from early research prototypes through obsolescence
* Ensuring open innovation through the sharing of the research, development, and maintenance efforts as far as possible
* Fostering exchanges between academics, standardization organisations, industry partners and community
* Organizing sustainable commercial services and ecosystems around those components
* Recognizing projects maturity and company know-how and commitment through a branding process available only to openMDM® Working Group Member organizations
\ No newline at end of file
---
title: "Related Eclipse Projects"
date: 2020-09-08T11:00:00-04:00
hide_sidebar: true
seo_title: "Related Eclipse Projects"
keywords: ["openmdm", "Related Eclipse Projects"]
---
The following Eclipse projects are related to the openMDM Working Group:
## 1. [MDM|BL](https://projects.eclipse.org/projects/technology.mdmbl)
The MDM|BL project comprises a bottom to top architecture view of three parts:
The first one is a specific openMDM application model definition for the ASAM ODS data storage. The standardization provides a structured representation for common use case related data in all openMDM application. The data model is split into the base model, which covers the most common use cases, and extensions for additional use cases.
The base model and every extension has an associated API interface. These interfaces are used by higher level components to work with openMDM business objects. In addition there are a set of business interfaces, which represent non data based enterprise use cases.
At the top of the layer there are the implementations of the business interfaces. In consideration of the API there normally will be an ODS server implementation but in some use cases the data storage is implemented otherwise. Virtual objects or the storage in an ODS ATFX file are examples.
Concerning the runtime view the business layer project defines a core application structure, which every openMDM application is based on. This structure is composed of services and rules how these services should be used and be executed at runtime.
Status: Incubation
Link: https://projects.eclipse.org/projects/technology.mdmbl
## 2. [MDM|WEB](https://projects.eclipse.org/projects/technology.mdmweb)
PLEASE NOTE THAT THIS PROJECT HAS BEEN ARCHIVED. IMPORTANT CONTENT HAS BEEN TRANSFERRED TO MDMBL
The MDM@WEB project includes multiple components for handling measured data. These components are structured to allow for high re-usability of core components like the communication with the ODS server or the import and export of data. In addition to these core components the project includes a web-based front-end.
The list of components includes:
* Navigator.
* Search (Meta-Data).
* Search (Full-Text).
* Export.
* Reporting.
* Shopping Cart (for interaction with local tools).
* Localization.
* User Documentation.
* Administration.
* Data Sharing.
* Archiving.
Status: Incubation
Link: https://projects.eclipse.org/projects/technology.mdmweb
\ No newline at end of file
---
title: "Specifications"
date: 2020-09-08T11:00:00-04:00
hide_sidebar: true
seo_title: "Specifications"
keywords: ["openmdm", "Specifications"]
---
In order to integrate openMDM® smoothly into your infrastructure, a few requirements have to be met. These are the specifications of the openMDM® system:
* As database management system (DBMS) openMDM® can use Oracle or MS SQL Server.
* openMDM® components run on the operating systems Windows and Linux.
* openMDM® is currently tested with the following ODS servers:
* [Avalon](https://www.highqsoft.com/avalon-asam-ods-server/)
HighQSoft GmbH, Schloßborner Weg 6b, 61479 Glashütten, Germany
* [Peak ODS Server](http://www.peak-solution.de/en/products-services/test-measurement-data-management/software-solutions/peak-ods-server/index.html)
Peak Solution GmbH, Lina-Ammon-Str. 22, 90471 Nuremberg, Germany
* openMDM® components are implemented in SUN Java from Version 1.5 and need the infrastructure required for it.
* openMDM® uses JacORB for implementation of the OMG's CORBA standard and OSGi to control the run time configuration.
\ No newline at end of file
---
title: "Collaboration"
date: 2020-09-08T11:00:00-04:00
hide_sidebar: true
seo_title: "Collaboration"
keywords: ["openmdm", "Working Groups", "Collaboration"]
---
Collaboration of the members is crucial for the success of a vital openMDM® Working Group. The Working Group commits itself to cooperation applying principles of openness, transparency and meritocracy.
The collaboration process is pointed out in the following diagram.
{{< figure src="/working-groups/images/collaboration.jpg" alt="collaboration process" >}}
&nbsp;
The collaboraton process includes:
* Annual Plan containing themes, marketing, outreach
* Definition of requirement packages and services modules
* Valuation of the defined packages with respect to estimated man power units, content and quality for their delivery
* Assignment of requirement packages and / or service modules to the WG members according to their openMDM® Working Group membership fees
* If there are no open membership fees left, voluntary donations of man power units by the openMDM® Working group members are welcome as well. Otherwise the required packages won’t be processed.
* The execution or delivery of the assigned packages are fulfilled independently by the respective member under its full responsibility and on its own expenses. The openMDM® Working Group will not act on behalf of its members.
* Acceptance of the corresponding services or results delivered by the openMDM® Working group members.
\ No newline at end of file
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment