1.
Bridging the Interoperability Gap
of the Internet of Things
BIG IoT Project – 2nd Webinar
Jelena Mitic
Stefan Schmid
Claudia Simonato

2.
2
We are …
Jelena Mitic
Project Coordinator
Siemens AG
Stefan Schmid
Architecture Lead
Bosch CR
Claudia Simonato
Open Call Task Lead
CSI Piedmont

3.
3
Agenda
 Project & Open Call Overview 10 min – Jelena
 BIG IoT Architecture 10 min – Stefan
 Q&A 10 min
 1st Open Call: How To Apply 15 min – Claudia
 Q&A 30 min

4.
4
For your information…
 The Webinar will be recorded
 Slides and recorded presentation will be available online
 Please post your questions in the chat, we will answer them in Q&A session
 Please mute your microphone during the presentation

5.
5
Project Overview
Jelena

6.
6
Challenge – missing interoperability
 Today, we are dealing with many heterogeneous, vertically oriented IoT platforms.
 Thus, the development of cross-platform and cross-domain applications is tedious and expensive.
 Additionally, it leads to high market entry barriers for small innovative business.
 As a result of this, no vibrant IoT ecosystem exists.

7.
7
Our approach
BIG IoT API
MarketplaceApplication Service
 BIG IoT API to provide and consume IoT resources from different platforms in an unify way
 Marketplace to share, discover and monetize IoT resources (data and services)
 Tool for easy development of new, cross- platform services and applications

8.
8
8 IoT platforms already speaks BIG IoT
Platforms
ConnectedCity Platform
Distributed Smart Object Platform
Smart Data Platform
Wubby Platform
OpenIoT Platform
Advanced Parking Management
TIC Platform
Smart Traffic Platform
Application
Application
…
Service
Service
…

9.
9
Pilots & Use Cases
Barcelona
Piedmont
Berlin – WolfsburgUse Cases in the domain of Smart Mobility
and Environmental Monitoring:
 Smart Parking
 Smart Traffic Management
 Public Transport Optimization
 Healthy Bike Navigation
 Smart Bike Sharing
 Incentive-based Green Route Planning
 Multimodal Route Optimization
 Smart Charging

10.
10
Project in a nutshell
Project Duration 01.01.2016 - 31.12.2018
Consortium 12 partners + 2 linked 3rd parties

11.
11
BIG IoT Open Calls
 €750k for 3rd parties to implement new IoT solutions or integrate the existing
ones into the BIG IoT ecosystem by making use of the BIG IoT enablers
 2 Open Calls:
 first
 Date: 26th Apr – 16th Jun 2017 – ONGOING
 Budget: €300k (up to €60k per project)
 second
 Date: Jan – Feb 2018
 Budget: €450k

12.
12
1st Open Call Summary
What?
Integrate existing IoT data sources/platforms by using BIG IoT API and offer them on
the BIG IoT Marketplace. The data sources should be related to Smart Mobility and
Environmental Monitoring.
Why?
 Join strong ecosystem , promote your solution, increase usage of your data for
new services and applications of the second Open Call, get visibility in the
European IoT community
When?
Call Open: 26th Apr – 16th Jun 2017
Project Implementation: Sep 2017- Jan 2018 (5 months)

13.
13
BIG IoT Architecture
Stefan

14.
14
Main Challenges
City – Public Parking
Department
Parking Lot Provider A
How to discover
data sources?
Parking Lot Provider B Berlin
Barcelona
Piedmont
Smart Parking
Service
How to access?
How to evolve?
…
Parking
Information
Community
-based
Parking

15.
15
Our Solution
City – Public Parking
Department
Parking Lot Provider A
Community
-based
Parking
Parking Lot Provider B Berlin
Barcelona
Piedmont
BIG IoT
Marketplace
Semantic
Description of
Offerings
Offering
Semantic
Search
Offering
…
Semantic
Description
Offering
Offering
Offering
Smart Parking
Service
Parking
Information

16.
16
High-level Architecture
Service / Application
Service / Platform
BIG IoT Marketplace
BIG IoT Provider Lib
BIG IoT Consumer Lib

17.
17
BIG IoT API – Access
BIG IoT
Provider
Lib
Credentials
<Output Data>
Generic
Offering
parameters
Offering
Description
<Input Data>
<response>
<platform call>
Call: Offering endpoint
Platform/Service

18.
18
Offering Description (OD)
Service / Application
Platform / Service
BIG IoT Marketplace
BIG IoT Provider Lib
BIG IoT Consumer Lib
OD describes
interface
OD used as payload
Offering
model
for
discovery

19.
19
Offering Description – Example
{ context: ["http://big-iot.eu/ctx" ,
{"schema" : "http://schema.org"}],
providerId: "Barcelona_City-provider"
name: "Sensor-level ParkingSpace Information"
category: "schema:parkingSiteManagement"
inputData: [
{name: "longitude", rdfType: "schema:longitude"}
{name: "latitude", rdfType: "schema:latitude"}
{name: "radius", rdfType: "schema:geoRadius"}
]
outputData: [
{name: "longitude", rdfType: "schema:longitude"}
{name: "latitude", rdfType: "schema:latitude"}
{name: "status", rdfType: "schema:parkingSpaceStatus"}
]
endpoints: { uri: "http://bigiot/access/parkinginfo", type: "HTTP_GET"}
licenseType: "OPEN_DATA_LICENSE", region: "Barcelona"...
price: { money: {amount: 0.002000, currency: "EUR"}, accountingModel: "PER_ACCESS"} }
...
URI of the
Offering
Semantic
annotations
Based on
Web of Things‘
Thing Description

20.
20
BIG IoT Marketplace ... for whom?
End User ... who are looking for apps
Developers, IT guys, Creatives…
• @ Smart City
• @ Mobility Company
… who need IoT offerings for their applications

21.
21
BIG IoT Marketplace

22.
22
BIG IoT Marketplace Portal

23.
23
Your tasks to integrate with BIG IoT
1. Utilize Provider Lib (currently in Java) to implement access to your Offerings
2. Utilize Provider Lib to implement interactions with Marketplace
3. Create Offering Description for each of your offerings to register them
a. Collaborate to extend the domain model to accomodate your offerings
4. Provide offerings at BIG IoT marketplace until end of BIG IoT project for all partners
5. Provide feedback and shape an IoT Ecosystem
Service / Platform
BIG IoT Marketplace
BIG IoT Provider Lib

24.
24
More information: Developer Guide

25.
25
Questions & Answers

26.
26
1st Open Call
How to Apply
Claudia

27.
27
Who
 Individual SMEs, universities, companies and research
institutes; only one entity per proposal; not necessarily
located in any of the three demonstration sites
 Not eligible for funding: institutions, organisations or
other kind of legal entities funded by otherwise affiliated
with a BIG IoT partner
 Each participant can present only one proposal
 Participants selected from the first Open Call can
participate to the second Open Call providing a value-
added solution
 Preferred data referring to pilot areas (Piedmont,
Barcelona, Berlin) PLEASE HIGHLIGHT THIS ASPECT IN
THE PROPOSALS!

28.
28
We are looking for…
 IoT Platform and Data providers
 Domains: Smart Mobility (traffic, parking
etc.) and Smart Environment (e.g. air
quality)
 Data (own or open source) – data won’t
become automatically open but BIG IoT
provides solutions for accounting, licensing,
and billing
 IoT Platforms that contain offerings/data
 Proposals in English
 Proposals up to €60k

29.
29
Important Applications Documents …
… are available at our website: http://big-iot.eu/first-open-call/

30.
30
How to participate - Application Form
F6S portal:
https://www.f6s.co
m/opencall1big-iot/

31.
31
Application Form I
Let us know who
you are!
Describe your profile
and create your
team.
Insert a complete
company profile.
Ask your team
members to login
into F6S.

32.
32
Application Form II
6 main sections:
A. Basic info
B. IoT Solution
C. Innovation and
Impact
D. Implementation
E. Data
management
F. Miscellaneous

33.
33
Focus: Section B- IoT Solution
Open data are NOT
MANDATORY.
BIG IoT enables
accountability that allow
the management of data
accordingly to the owner’s
policies.

34.
34
Focus: Section D Implementation
Duration: Up to 5 months
Deliverables: any tangible
output (report, software etc.
describing your results).
List of deliverables template
avilable on our website.
2 deliverables are
MANDATORY for proceeding
the scheduled payments :
Intermediate and
Final Technical Report.
Budget for personnel,
equipment and other goods,
services and travel costs.

35.
35
And then?
Submission Deadline
June 16, 5pm CET
Evaluation by external evaluators and
notification of winners:
End of July
Project start:
September 1, 2017
Winners will join the project as Siemens third parties
and sign the Collaboration Agreement with Siemens.

36.
36
Communication and support
During the proposal phase:
 FAQ section on our website
 Feasibility Check for proposals draft
available until the 9th of June
 Helpdesk e-mail contact
During the implementation phase:
 Kickoff F2F meeting beginning of
September in Munich
 First support team:
 Open Call team: Claudia & Jelena
 Technical team lead by Arne

37.
Thank you for your attention!

38.
38
Questions & Answers

39.
39
be part of our BIG team