33
© 2017 – The symbIoTe Consortium Webinar on 1 st Open Call symbIoT e 16 February 2017 Grant Agreement No 688156

Webinar on 1st Open Call - slideset

Embed Size (px)

Citation preview

© 2017 – The symbIoTe Consortium

Webinar on 1st Open Call

symbIoTe

16 February 2017

Grant Agreement No 688156

© 2017 – The symbIoTe Consortium2

Meet the team!

Julia Wells

Open Call Assessment

ATOS

Maria Bianco

Open Call Manager

CNIT

Ivana Podnar Zarko

Technical Manager

UNIZG-FER

Sergios Soursos

Project Coordinator

ICOM

© 2017 – The symbIoTe Consortium3

Agenda

Time Session Presenter

11:00 – 11:05 Welcome & Logistics Julia

11:05 – 11:20 Project overview & Open Call summary Sergios

11:20 – 11:35 Technical Approach Ivana

11:35 – 11:45 Q&A

11:45 – 12:00 Management Issues Maria

12:00 – 12:10 Q&A, Feedback

12:10 End of Webinar

© 2017 – The symbIoTe Consortium4

• The webinar will be recorded

• Slides and video will be made available through our web site (Slideshare and YouTube)

• To ask questions please use the chat/IM and we will take questions in Q&A periods

• Please mute your microphones!

Logistics

© 2017 – The symbIoTe Consortium

Project overview and 1st Open Call summary

symbIoTe

Sergios Soursos, Intracom SA Telecom Solutions

Project Manager

Grant Agreement No 688156

© 2017 – The symbIoTe Consortium6

• IoT platforms offer vertical solutions, closed silos– focusing in one domain

• Absence of cross-domain apps– life is multi-dimensional– partnerships sought

• Collocated platforms– multiple installations– increased costs

• Maintenance of e2e solutions– high market entry barrier– will a single standard/technology/protocol prevail?

• End users– vendor lock-in– multiple apps

IoT Landscape & Motivation

© 2017 – The symbIoTe Consortium7

• symbiosis of smart objects across IoT environments

• interoperability and mediation framework

• aims at the collaboration of vertical IoT platforms towards the creation of cross-domain applications

The symbIoTe Approach

Smart Residence

EduCampus

Smart Stadium

Smart Mobility and Ecological Routing

Smart Yachting

© 2017 – The symbIoTe Consortium8

symbIoTe in a Nutshell

• not yet another IoT platform

• a middleware that offers a unified way for– exposing of IoT resources to third party applications

– sharing IoT resources between federation members

– trusted discovery and secure access to IoT resources

– flexible integration of smart space infrastructure

– does not interfere with the actual data exchange

• addresses the needs of – developers for rapid cross-platform application

development

– small IoT platform providers for optimal collaboration and cooperation on top of the available often fallow resources

– SMEs for overcoming IoT market barriers

© 2017 – The symbIoTe Consortium9

Becoming symbIoTe-enabled

Application

Domain

Cloud

Domain

Smart Space

Domain

Smart Device

Domain

Gateway

Smart DevicesSmart DevicesSmart DevicesSmart Devices

Platform BackendInterworking API

IoTPlatform A

symbIoTe Core ServicesCore API

IoTPlatform B

IoT Applications 1

2

© 2017 – The symbIoTe Consortium10

Exposing resources – example

symbIoTe Core ServicesCore API

IoTPlatform A

IoTPlatform B

Temperature sensor “X” atcoordinates

(… , …)

“Room A Temperature”

service of room at building “Z”

• How can platforms monetize the value of their resources? new revenue streams!

• How can 3rd parties use the offered resources?

© 2017 – The symbIoTe Consortium11

• IoT solution providers

– SMEs, startups, companies, research institutes

– w/ deployed IoT platforms

– active in Smart Home/Building and Smart Cities

• 3 important questions

– What resources can you open to 3rd parties?

– How 3rd parties can use your resources?

– What value will the 3rd parties make out of your resources?

What are we looking for?

© 2017 – The symbIoTe Consortium12

• Decide what resources to open

• Provide information model of resources

• Extend Interworking API

– use generic components, and

– implement platform specific components

• Proof-of-concept showcase

– together with symbIoTe consortium

– advertise own resources

– make them discoverable through Core Services

What will you have to do?

© 2017 – The symbIoTe Consortium13

• For symbIoTe

– enrich the portfolio of symbIoTe-enabled platforms

– receive feedback on designed solution

– build the foundations for the 2nd Open Call

• For applicants

– investigate what resources you could open to 3rd

parties

– see what value you can get out of it

– ease the partnerships with other platforms

Objectives

© 2017 – The symbIoTe Consortium

Technical Approach for Level 1 Compliance

symbIoTe

Ivana Podnar Žarko, University of Zagreb

Technical Manager

Grant Agreement No 688156

© 2017 – The symbIoTe Consortium15

Level 1 compliance (L1)

• symbIoTe: intermediary between IoT platforms and applications– facilitates cross-platform app development

– syntactic: interoperability at the protocol level

– semantic: interoperability at the data level

• Create cooperative IoT platforms– IoT platforms open up access to their devices (exposed as

services) in a controlled and secure manner

• Enable devices to understand each other– apps need to understand platform offerings/virtualized

devices (to a certain extent) to interact with them

Technical Aspects

© 2017 – The symbIoTe Consortium16

• Mobile app as a remote control to switch on/off the lights at home, in the office, in public spaces…

– today we need 3 apps for this, one for each platform

Motivating example (actuation)

© 2017 – The symbIoTe Consortium17

symbIoTe-enabled Ecosystem

Smart Space

Domain

Smart Device

Domain

symbIoTe Core Services

Enablers’ space

IoT Platform Backend

IoT devices, gateways and other resources

Interworking Interface

IoT Devices

Core Interface

Cross-Domain Apps

Domain-specific Interface

Application

Domain

Cloud

Domain

Cross-Platform Applications

sym

bIoT

e-en

able

d pl

atfo

rm

1st open Call

© 2017 – The symbIoTe Consortium18

Syntactic & Semantic Interoperability (L1)

3. Direct access

and usage of

devices

(as services)

symbIoTe Core Services

Cross-Platform Application

IoT Platform A

Interworking Interface

Core Interface

IoT Platform B

Interworking Interface

22. Search for adequate

devices

33

Core Information

Model:

stores device metadata

Platform-Specific Information

Model compliant to the Core

Information Model:

full definition of devices, their data

and primitives

RESTful API based on OData (OASIS standard) or NGSI v2

(FIWARE)?:

access to device data and

primitives (for actuation)111. Register

devices

© 2017 – The symbIoTe Consortium19

L1 Components

Asynchronous messaging

Platform 1 Platform 2

Sensors, Actuators

Registration Handler

RegistrySearchEngine

CoreRAM

Applications

Core Interface

RAP RAP

Admin. Core RM

Cloud-Core Interface

Sensors, Actuators

Interworking Interface

MonitoringRegistration

HandlerMonitoring

PAAM

PAAM

Core AAM

Interworking Interface

Core Services

search

register

useuse

register

© 2017 – The symbIoTe Consortium20

Technologies and Licenses

Platform 1

Sensors, Actuators

Core Services

symbIoTe is open source: https://github.com/symbiote-h2020

L1 Platform Services

microservices

microservices

Eureka

LGPL-3.0 license

BSD-3-Clause

© 2017 – The symbIoTe Consortium21

To make a platform Level 1 compliant:• Analyze the symbIoTe Core Information Model

(CIM) and symbIoTe components on the platform side

• Align your platform-specific information model with the CIM – Use JSON if CIM is sufficient for your needs

• Integrate the Interworking Interface and four symbIoTe components with your platform– plugins for closed platforms will not be published as

open source

• Provide feedback and comments to improve and simplify the process of creating L1 platforms

How to create a L1 platform?

© 2017 – The symbIoTe Consortium22

• A documented design and prototype implementation of the symbIoTe Core Services

• A documented Interworking Interface and Java implementation of the four components on the platform side

• An example procedure for aligning an existing information model to the symbIoTe CIM

• A documented example explaining the process for creating a L1 platform based on the example of the open-source OpenIoT platform

What do we offer?

© 2017 – The symbIoTe Consortium23

• Read our technical blog entrieshttps://www.symbiote-h2020.eu/index.php/tech-blog/

• More technical details– 1st Open Call - Technical Details

– symbIoTe Deliverables: D1.2, D2.1 and D2.2

• https://github.com/symbiote-h2020– Release 1: mid February 2017

– Release 2: End April 2017

For more information

© 2017 – The symbIoTe Consortium

Thank you!

Questions?

www.symbiote-h2020.eu

[email protected]

@symbiote_h2020

H2020 symbIoTe

github.com/symbiote-h2020

© 2017 – The symbIoTe Consortium

Management Issues

symbIoTe

Maria Bianco, CNIT National Inter-University Consortium for Telecommunications

Open Call Compliance

Grant Agreement No 688156

© 2017 – The symbIoTe Consortium26

www.symbiote-h2020.eu

How to apply

Open Call Documentation

Access to F6S Platform

https://www.f6s.com/opencall1symbiote

© 2017 – The symbIoTe Consortium27

• Eligibility Criteria– Start ups, SMEs, companies or research

institutes/organizations, with legal entity already established

– European Member States and Associated Countries

• Funding conditions– Total Budget : 120.000 euros

– Max Funding per Extension: 40.000 euros

– Eligible costs: Personnel and Travel costs

• Deadline: 28° Feb 2017 17:00 CET (Brussels time)

Main Constraints

© 2017 – The symbIoTe Consortium28

Application details (I)

Describe your profile and Create your Team!

Who you are and tell us about your team –provide a complete Company profile!

- 2 or 3 Key Expertise - Established

company/start-up

Ask your co-workers to login into F6S

© 2017 – The symbIoTe Consortium29

Application details (II)

6 Main Sections

Auo-Save Functionality: do not press SUBMIT before the Application is finalized

Limited number of Characters

A. Basic InfoB. IoT SolutionC. Innovation and ImpactD. ImplementationE. Data ManagementF. Miscellaneous

© 2017 – The symbIoTe Consortium30

Application details (III)

Focus: Section D. Implementation

DURATION: Up 6 Months

DELIVERABLE: any tangible output (Report, Software or Report + Software) describing your results

2 Additional Deliverables are MANDATORY for proceeding the Scheduled Payments !! 1. Intermediate Report2. Final Report

Template available in symbIoTeStandard Extension Contract

TRAVEL: You will be invited to attend a symbIoTe Meeting

© 2017 – The symbIoTe Consortium31

Access to Background information from the project

• Results are owned by the Party or by the symbIoTe Beneficiary thatgenerates them

• Joint Ownership of results: Third Party and Beneficiaries contributing in aindivisible part of the results -> jointly owned by them in equal shares ordifferently ruled with a joint ownership agreement

• Access Rights to Background: only if needed for implementation of theExtension. Where this is the case, the Selected Third Party will haveAccess Rights to that Background on royalty-free basis, solely to the extentNeeded to implement its tasks in the Extension;

• Ruled by the Agreement between Third Party and symbIoTe Coordinator– symbIoTe Standard Extension Contract

IPR Management: Principles

© 2017 – The symbIoTe Consortium32

• Evaluation

– Independent and external experts

– Evaluation Criteria available on symbIoTe web site

• Communication of Funding: Beginning of APRIL

• Support in Implementation phase by symbIoTe

– Supporting Team: 1 technical champion and 1 businesschampion

– an initial briefing in order to discuss and focus the work tobe performed during the Extension.

– Selected Third Parties can contact the Supporting Team onper-need basis on technical and business matters.

After the Deadline?

© 2017 – The symbIoTe Consortium

Thank you!… and Good Luck!

Questions?

www.symbiote-h2020.eu

[email protected]

@symbiote_h2020

H2020 symbIoTe

github.com/symbiote-h2020