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.
Difference between revisions of "BaSyx / Documentation"
(Created page with "== Architecture overview == The BaSys 4.0 project defines the following main component types: {| class="wikitable" |- ! Component type ! Description |- | Control component...") |
m (Proper image formatting) |
||
| Line 41: | Line 41: | ||
| − | [[file:BaSyx.Architecture_Overview.png]] | + | [[file:BaSyx.Architecture_Overview.png|center|1024px]] |
| Line 50: | Line 50: | ||
| − | [[file:BaSyx.Architecture_Interfaces.png]] | + | [[file:BaSyx.Architecture_Interfaces.png|center|1024px]] |
Revision as of 10:34, 28 August 2018
Architecture overview
The BaSys 4.0 project defines the following main component types:
| Component type | Description |
|---|---|
| Control component | Provides a conforming BaSys 4.0 service based interface that enables access to device capabilities. |
| Group component | Provides higher-level services that use services of other control and group components. |
| Gateway | Protocol gateway that bridges five BaSys communication primitives between protocols to enable end-to-end communication. |
| Asset Administration Shell | An Asset Administration Shell (AAS) is a digital object that represents a physical or non-physical entity. It stores all relevant data and provides access to operations through its sub models. |
| Asset Administration Shell sub models | Sub models are part of one Asset Administration Shells. They consist of (optionally nested) properties and operations. AAS sub model providers provide different kinds of data as AAS sub models. |
| Registry / Discovery | The registry/discovery component enables registration and lookup of Asset Administration Shells. |
| Strategy / Optimization | The Strategy/Optimization component calculates production plans and production schedules that define when, and on which machine a production step for a specific product will be executed. |
| Process control | The process control component executes the production plans that the Strategy/Optimization component did create. |
| Monitoring | The monitoring component enables the monitoring of the production process. It for example collects and aggregates data for analysis or pushes selected and aggregated data to a dashboard. |
The graphic below illustrates the components of a BaSys 4.0 production system. Components connect to a virtual end-to-end communication medium that in fact may be realized with different networks and protocols. Communication is via defined primitives that are mapped to each protocol in a specific manner. Gateways bridge between protocols and enable a virtual end-to-end communication.
Component interfaces
Interfaces are well-defined interaction points in the BaSys 4.0 architecture. They enable the substitution of component implementations and the development of conforming implementations by 3rd parties. BaSys 4.0 components and BaSyx components define HTTP-REST interfaces on middleware and plant levels, as well as OPC-UA and native TCP BaSyx interfaces on device level.
BaSys 4.0 conforming components need to implement the interfaces shown in the above figure and the following table. The BaSyx platform provides a reference implementation for core components that are necessary to create and deploy an Industrie 4.0 solution.
| Component type | Necessary provided interfaces | Interface type |
|---|---|---|
| Control component | RTE Management, Service status, Service selection, Service invocation | OPC-UA, BaSyx native |
| Group component | RTE Management, Service status, Service selection, Service invocation | OPC-UA, BaSyx native |
| Gateway | Gateway | Any to any |
| Asset Administration Shell | AAS | HTTP-REST |
| Asset Administration Shell sub models | Sub model | HTTP-REST |
| Registry / Discovery | Discovery, Registry | HTTP-REST |
| Strategy / Optimization | --- | HTTP-REST |
| Process Control | Process management, Process execution | HTTP-REST |
| Monitoring | --- | HTTP-REST |
Strategy / optimization and Monitoring components are highly plant specific. These components use provided interfaces of other BaSys 4.0 components, but are not required to provide defined BaSys 4.0 interfaces.