Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

BaSyx / Documentation / Models

< BaSyx ‎ | Documentation
Revision as of 15:48, 9 March 2020 by Thomas.kuhn.iese.fraunhofer.de (Talk | contribs) (Created page with "Models, e.g. the Asset Administration Shell and its sub models are a major part of Eclipse BaSyx. They provide defined interfaces to data, processes, entities and services in...")

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Models, e.g. the Asset Administration Shell and its sub models are a major part of Eclipse BaSyx. They provide defined interfaces to data, processes, entities and services in production environments, and are therefore a core asset of BaSyx. Meta-models define the structure of a model, and therefore the structure of asset administration shells and sub models. This section of the Eclipse BaSyx Wiki collects meta models for sub-models to support developers with reference models. The meta models provided in this section are grouped into standardized sub models, meta models in standardization, recommended meta models, and meta models that are provided here as reference without a specific recommendation.

Standardized sub models have been standardized by a recognized standardization organization. Meta models in standardization have not yet been standardized, but have been submitted to standardization or are developed and have at least been published once by an organisation that is recognized by standardization bodies as organization that provides ready-to-be standardized documents. These usually cover boards that consist of numerous members from industry and academia, like the working groups of the Platform Industrie 4.0. Recommended meta models are recommended by the BaSyx committers to be used for a specific application. Unrated meta models are meta models that are collected on this site, but did not yet receive a recommendation by BaSyx. This does not mean that a model is bad. Probably it has not yet been processed by the BaSyx team or it covers a specific aspect of the production.

A meta model can be provided in different formats that are usable by BaSyx model providers. Currently, BaSyx supports XML files, JSON files, and OPC-UA sub models. Optionally, a descriptive technology independent documentation may be provided for a meta model.


Standardized meta models:

Name Documentation XML JSON OPC-UA


Meta models in standardization:

Name Documentation XML JSON OPC-UA


Recommended meta models:

Name Documentation XML JSON OPC-UA


Unrated meta models:

Name Documentation XML JSON OPC-UA

Back to the top