Skip to main content
Jump to: navigation, search

Difference between revisions of "BaSyx / Submodels"

(Added Control Component Submodels. Restructured list with headings to enable linking and automatic toc.)
Line 1: Line 1:
 
On this page, we collect sub models. The page is not yet linked from the wiki.
 
On this page, we collect sub models. The page is not yet linked from the wiki.
  
* Platform resources sub-model
+
== Platform resources submodel ==
** in AP1 D1.3
+
* in AP1 D1.3
** involved: Tarik Terzimehic (fortiss), Sten Grüner (ABB), Thomas Kuhn (IESE), Frank Schnicke (IESE), ...
+
* involved: Tarik Terzimehic (fortiss), Sten Grüner (ABB), Thomas Kuhn (IESE), Frank Schnicke (IESE), ...
** [https://abb.sharepoint.com/sites/BaSys42/Shared%20Documents/Forms/AllItems.aspx?viewid=52ae1613%2D6223%2D41a3%2D9dba%2D45682aade7b7&id=%2Fsites%2FBaSys42%2FShared%20Documents%2FArbeitspakete%2FAP1%2FD%2D1%2E3%20Plattformressourcen Link to deliverable and workspace]
+
* [https://abb.sharepoint.com/sites/BaSys42/Shared%20Documents/Forms/AllItems.aspx?viewid=52ae1613%2D6223%2D41a3%2D9dba%2D45682aade7b7&id=%2Fsites%2FBaSys42%2FShared%20Documents%2FArbeitspakete%2FAP1%2FD%2D1%2E3%20Plattformressourcen Link to deliverable and workspace]
 +
 
 +
== Control Component Type ==
 +
* Short description: Collects information of a control component type, e.g. semantic descripton of operation modes, profile, link to capabilities, error codes
 +
* in AP4, "Orchestration and Control Component Submodel Telko"
 +
* responsible: Julian Grothoff(RWTH), Michael Thies(RWTH)
 +
* involved (alphabetical order): Sten Grüner(ABB), Tobias Klausmann(Lenze), Daniel Porta(DFKI), Gerhard Schaller (ZF), Tarik Terzimehic (fortiss), Constantin Ziesche (Bosch)
 +
* [https://abb.sharepoint.com/:f:/r/sites/BaSys42/Shared%20Documents/Arbeitspakete/AP4/Orchestrierung%20und%20CC%20Teilmodell?csf=1&web=1&e=cwrphf Link to deliverable and workspace]
 +
 
 +
== Control Component Instance ==
 +
* Short description: Collects information on control component instances, e.g. endpoints, available or disabled states or modes, configuration
 +
* See [[#Control Component Type]] for organizational information
 +
 
 +
== Control Component Interface ==
 +
* Short description: Shows the current states and offers operations to manipulate them according to [[BaSyx_/_Documentation_/_API_/_ControlComponentProfiles#SI_Facet_OPERATIONS|operations interface specification]]. Can be realised as proxy to an existing control component or as an implementation of the control component itself.
 +
* See [[#Control Component Type]] for organizational information
 +
 
 +
== Control Component Services ==
 +
* Naming is in discussion, maybe "macros" or "high level service" is more suitable
 +
* Short description: Offers a highlevel interface with services or macros, that are often used or helpfull for specific use cases like maintenance, e.g. "occupy --> select operation mode --> start --> wait to complete" sequence.
 +
* See [[#Control Component Type]] for organizational information

Revision as of 09:23, 8 December 2020

On this page, we collect sub models. The page is not yet linked from the wiki.

Platform resources submodel

Control Component Type

  • Short description: Collects information of a control component type, e.g. semantic descripton of operation modes, profile, link to capabilities, error codes
  • in AP4, "Orchestration and Control Component Submodel Telko"
  • responsible: Julian Grothoff(RWTH), Michael Thies(RWTH)
  • involved (alphabetical order): Sten Grüner(ABB), Tobias Klausmann(Lenze), Daniel Porta(DFKI), Gerhard Schaller (ZF), Tarik Terzimehic (fortiss), Constantin Ziesche (Bosch)
  • Link to deliverable and workspace

Control Component Instance

  • Short description: Collects information on control component instances, e.g. endpoints, available or disabled states or modes, configuration
  • See #Control Component Type for organizational information

Control Component Interface

  • Short description: Shows the current states and offers operations to manipulate them according to operations interface specification. Can be realised as proxy to an existing control component or as an implementation of the control component itself.
  • See #Control Component Type for organizational information

Control Component Services

  • Naming is in discussion, maybe "macros" or "high level service" is more suitable
  • Short description: Offers a highlevel interface with services or macros, that are often used or helpfull for specific use cases like maintenance, e.g. "occupy --> select operation mode --> start --> wait to complete" sequence.
  • See #Control Component Type for organizational information

Back to the top