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

< BaSyx ‎ | Documentation
Revision as of 06:20, 20 January 2020 by J.grothoff.plt.rwth-aachen.de (Talk | contribs) (Moved profile sections from BaSyx_/_Documentation_/_API_/_ControlComponent)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Warning2.png
This information is work in progress as part of the BaSys 4.2 project. This section is preliminary and subject to change during the project.


Overview | Interface | Implementation

The abstract concept of control components and their state machines may be realised in technology specific ways or focussed on certain aspects. For example an occupation might not be necessary or a smaller execution state machine may be satisfying. Especially domain, task or company specific constraints may need to be applied in brownfield scenarios. In order to describe basys control components in a standardized manner and to ensure the compliance of basys labled control components, possible realisation types are clustered in profiles. These profiles may be used for the typification und type description of control components. Furthermore, they can be used to define requirements of a component system or its orchestration environment.

One goal of BaSys 4.2 is to enable plug and produce scenarios via standardized procedures. Considering that, the requirements of heterogenous industrial production systems and the offered features of various control components need be described and matched. In order to support this matching in an automated manner a limitation and standardization to usefull profiles is necessary. Combinations of commonly used profiles will be used to define integration variants for easier commponent development and usage. Finally adapters may be generated to integrate components of different profiles.

In conclusion control component profiles describe which design patterns are used for a control component or its type in a standardized manner. Hence they are linked to the basys design patterns which rely on the control comopnent state machines. The goal is to reference existing standards and to build a bridge between component creators and their users. In the context of I4.0 it is recommended to use the control component submodel in the asset administrator shell (AAS) to describe required or assured profiles of a control component.


Back to the top