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 / Status

< BaSyx
Revision as of 11:56, 28 August 2018 by Thomas.kuhn.iese.fraunhofer.de (Talk | contribs) (Added intra-project navigation)

This section lists the status of main BaSys functions and components. Over time, additional features and components will be added.


Currently, BaSyx realizes support for BaSys 4.0 Asset Administration Shells, Sub models, protocol gateways, Industrie 4.0 applications, and interface devices via its SDK. Registry/directory, process control, and sub model providers are supported via open-source components. Reference examples that implement monitoring components are provided as well.


Component status description

  • ok: The code is developed, tested, and covered by regression tests.
  • wip: You might find code in the git repository, but it is considered unfinished and not yet tested.
  • tbd: Work has not yet started on this component or only little effort is currently allocated at developing this component
  • n/a: This feature is not planned for this SDK


SDK Features (Asset Administration Shell, Sub models, Gateway) Java C++
Support for developing Asset Administration Shells and sub models ok ok
JSON Serialization of AAS and sub model properties ok ok
Consistent cut accross multiple AAS / sub models ok tbd
Exception notifications tbd tbd
Gateway development ok n/a
AAS caching ok tbd
Active AAS ok tbd


The BaSyx SDK supports the development of Asset Administration Shells (AAS), the development of sub models, and the development of protocol gateways. Currently, BaSyx SDK is supported for Java and C++, C# is under development.


BaSyx open source component
Registry/Discovery wip
Process control (Activiti) wip
Monitor (Eclipse Grafana integration) wip
AAS sub model provider
SQL provider wip
CFG provider wip
Excel provider wip
JSON provider wip
XML provider wip
AutomationML provider wip
File system provider wip

BaSyx open source components implement various components of the Industrie 4.0 middleware layer. We expect the BaSyx open source components in wip state to move to ok state in October 2018.


BaSyx sub model types are ready-to use frameworks that implement recommended and mandatory BaSys sub model type definitions.


BaSyx sub model types
Topology wip
Capability wip
Identification wip


BaSyx project links: Project BaSyx main wiki page | What is BaSyx? | BaSyx Developer Documentation

Back to the top