BaSyx / Status
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 creating and using Asset Administration Shells, distributed Submodels, protocol gateways, Industrie 4.0 applications, and interface devices via its SDK. Registry, process control, and Submodel 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, Submodels, Gateway)||Java||C++||.NET|
|Support for developing Asset Administration Shells and sub models||ok||ok||ok|
|JSON serialization of AAS and Submodel properties||ok||ok||ok|
|Consistent cut across multiple AAS / Submodels||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|
|Process control (Activiti)||wip|
|Monitor (Eclipse Grafana integration)||wip|
|AAS sub model provider|
|File system provider||ok|
BaSyx open source components implement various components of the Industrie 4.0 middleware layer.
BaSyx sub model types are ready-to use frameworks that implement recommended and mandatory BaSys sub model type definitions.
|BaSyx sub model types|