===== Klausur tagung =====
==== Session 1 ====

**ISCO** 
    * more generic: semantic, service domain. Chariot will deal more with device layer.
    * Sahin: ISCO should focus on embedding hardware objects in software smart objects.
    * FK: VDI drive ISCO to more service orchestration platform / domain. Project name was also updated accordingly.
    * Sahin: still we want scalable middleware that meet the scale of HW devices.

**CHARIOT**
    * Sahin: Scalable Middleware and application area.
      * Select application --> increase value of the project.
    * FK: We turn our lab in to testbed, deploy in our building: workplace, factory. POC deployment.
    * TD (think): something like Gent testbed.
    * Marco: simulation of service (FK: for robotic usecase)

  * Sahin: runtime env (WP2), iolite integrate simple, constrained device. On top we build jiac high lever servcie for more powerful, quality services (IO-Lite++) as outcome of the project. 
    * IO-Lite bus / middleware (details on middleware).
  * Sahin: usecase should focus on domain areas, which we can find partner and ad ourself. Implementing all scenarios are too much effort.
  * Marco: the other usecase can be simulated.
  * FK: bulding and industrie scale usecase. Some focus on industry 4.0, work place with robots (Can).
  * Sahin: Industry 4.0 is about production pipeline, partly included robots (as machine not service robots).

==== Session 2 ====
**GT-ARC work program
**  * Advanced Tech research
    * Basic research with close to reality application result.
    * Scientific impact.
    * Closed bmbf program.
  * Applied research & dev program
    * Cooperation with industry using previous projects.
    * Open calls: bmbf, ..., we have testbed, software component, etc, which can be used in your workpackage.
  * GT-ARC Steering committee: Technological focus: smart city, cybersecurity

**Project's shared goals, Strategic Outcomes and Assets" - by Fikret/Can**

**ISCO**

  * CAN: isco assets extend DAI projects
  * Sahin: Main outcome of ISCO should be fundamental outcomes: modeling smart city object, API. 
    * Nils: VSDT focuses on service orchestration, we may extend the framework to smart object domain in ISCO.
    * Sahin: how to describe object?
      * Nils, Can: but this should be focus of chariot.
      * Sahin: abstract / description of object should be in the results of the project ISCO. All team, Nils, Johannes will have meeting with project carriers (?) to discuss smart object description.

**Chariot**
  * Robot integration should be side activity.

**Strategic outcomes Publication**
  * Sahin: Fikret supports.
  * Sahin: focus on main activity, project success.
  * Sahin: encourage new project ideas, proposals.