2. 1
e-business Web 2.0 Smart Life
Presence of business
on Internet
(B2C, B2B)
Presence of people
on Internet
(Social Networks)
Improving daily life
of people and businesses
(Smart X)
We are in front of a new Digital revolution which will transform the daily
life of people and businesses: everything that can be connected will be
connected, for the sake of a more smart life
3. 2
The new Digital Life will gravitate around context data. Context
data which describes what is going on, where, when, why …
4. 3
… in Cities
Bus
• Location
• No. passengers
• Driver
• Licence plate
Citizen
• Birthday
• Preferences
• Location
• ToDo list
Shop
• Location
• Business name
• Franchise
• offerings
5. 4
Tractor
• Location
• Speed
• Direction
Crop
• Humidity
• Leaf area
• Age
Drone
• Location
• Battery level
• Speed
• Direction
… in Agrifood
6. 5
Tanker
• Driver
• Location
• Max Volume
• Current Level
• Speed
• Direction
Gas Tank
• Station
• Max Volume
• Current Level
• Min Threshold
• Temperature
Station
• Location
• Owner
• SLA
… in Industry
7. 6
Context creates a digital continuum, blurring the frontiers between application domains
Breaking the current silos of information
8. 7
e-business Web 2.0 Smart Life
Presence of business
on Internet
(B2C, B2B)
Presence of people
on Internet
(Social Networks)
Improving daily life
of people and businesses
(Smart X)
10. 9
FIWARE: The Open Source platform of choice for
building smart solutions
Smart Solutions gather data from many different sources (including
but not limited to IoT) to build a “picture” of the real world and then
process and analyze that information in order to implement the
desired intelligent behavior (which may imply changing the real world)
Data =
Context Information
Capture
Actuate Process
11. 10
What if ...
for accessing
context information?
a standard API
there were
13. 12
Context Broker
Standard API
GET <Oauth token>
/V1/contextEntities/lamp1/attributes/presenceSensor
Reading the value
provided by a sensor
should be as easy as
reading an attribute of
an entity
“I don’t care what
low-level IoT protocol
is used”
“I should not need to
handle connectivity
with IoT devices”
IoT would be an enabler, no barriers because of
complexity
14. Actuation on a device
should come as a side
effect derived from
updating the attribute
of an entity
PUT <Oauth token>
/V1/contextEntities/lamp1/attributes/status “light on”
IoT would be an enabler, no barriers because of
complexity
13
Context Broker
Standard API
“I don’t care what
low-level IoT protocol
is used”
“I should not need to
handle connectivity
with IoT devices”
15. Shared context information would boost innovative services
and the development of a Data Economy
§ Organizations in different domains could
interchange data based on a common Context
Information Management layer
§ Authorization and Access Control Policies govern
who can access what, when (Sovereign of Data)
§ Organizations may monetize the data they offer
(Economy of Data)
14
Smart
Factory
Smart
Bank
Smart
Retail
Smart
Home
Smart
City
Virtual Shared Data Space
Smart
Servicesstandard
API
FIWARE NGSI and Context Broker
Technology has been selected to
become a CEF (Connecting Europe
Facility) Building Block
16. Entrepreneurs will benefit the opportunities of a larger
market
15
“We can invest on
development of
solutions we don’t
have to adapt for each
and every customer”
17. FIWARE: Driving the standard for Context Information
Management
§ FIWARE NGSI is a simple yet powerful public, royalty-free standard API for Context
Information Management
§ A RESTful API using JSON so any web/backend programmer gets quickly used to it
§ Yet powerful: FIWARE NGSI supports geo-queries, soon Linked Data (JSON-LD)
16
Application/Service
Bus
• Location
• No. passengers
• Driver
• Licence plate
Citizen
• Name-Surname
• Birthday
• Preferences
• Location
• ToDo list
Shop
• Location
• Business name
• Franchise
• offerings
Context Information
FIWARE NGSI API
18. 17
The GSMA has published
a Reference Architecture
for IoT Big Data
Ecosystem which
recommends to mobile
operators
FIWARE NGSIv2 should
be supported by
implementers delivering
the IoT Big Data
ecosystem
TM Forum, the global
industry association for
digital business, is working
with FIWARE to deliver the
key building blocks for
enabling and connecting
Smart City ecosystems.
TM Forum is supporting
the FIWARE NGSI APIs for
real-time access to context
information in cities.
ETSI has announced the
creation of a new Industry
Specification Group on
cross-sector Context
Information Management
(ISG CIM) for smart cities
applications and beyond.
FIWARE NGSIv2 is the
starting point for the CIM
API to be specified
FIWARE: driving the standards for Context Information Management
19. Integration with sensor networks
§ FIWARE NGSI is capable to deal with the wide variety of IoT protocols today
§ Rather than trying to solve the battle of standards at IoT level, it brings a standard where no
standard exists today: context information management
18
FIWARE Context Broker
FIWARE NGSI API (northbound interface)
IoT
Agent-1
IoT
Agent-2
IoT
Agent-n
IoT Agent
Manager
create/monitor
FIWARE Backend IoT
Device Management
(southbound interfaces)
OPC UA MQTTIETF CoAP
OMA LWM2M
FIWARE IoT platform
components or alternative
IoT platform supporting
connection to Context
Broker technology
20. Open data publication
Once context information is gathered, other useful
FIWARE enablers can be used
19
Advanced Web-based UI
(AR, 3D)
Data/Apps visualization
Big Data AnalysisComplex Event
Processing
Multimedia processing
IoT-enabled
Context Information
Management
22. Kurento
§ Kurento is a WebRTC
media server and a set of
client APIs making simple
the development of
advanced video
applications
§ Kurento Media Server
features include group
communications,
transcoding, recording,
mixing, broadcasting and
routing of audiovisual
flows
21
23. Cygnus and STH Commet
§ Cygnus enable to persist historic context information
into:
§ HDFS, the Hadoop distributed file system.
§ MySQL and PostgreSQL, the well-know relational database
managers.
§ CKAN, an Open Data platform.
§ MongoDB and STH (Short-Te r mHistoric)
§ Kafka queues
§ DynamoDB, the cloud-based NoSQL database
§ CartoDB, the geolocated platform
§ STH Commet provides a MongoDB context data storage
for short-term context information history
§ Fast response for queries on short-term context information
history
22
24. WireCloud - Dashboards
§ Fully customizable and extendable by the
development of new widgets and operators
§ Ready-to-use support for the FIWARE’s data models
§ Share your dashboards with specific users or make
them public. Moreover, your can embed your
dashboards on third-party web pages
23
25. Cosmos BigData
§ The Cosmos BigData Analysis GE is intended to bring
tools enabling analysis of both batch and stream context
information
§ Batch analysis relies on Hadoop (which may be based
on OpenStack’s Sahara or be a customized Hadoop
deployment) and Cosmos brings some added features:
§ User Accounts Management
§ OAuth2 authorization and access control support
§ REST APIs for MapReduce jobs submission and
management
§ Stream analysis relies on Storm and Cosmos brings an
intuitive graphical interface for:
§ programming analysis algorithms
§ management of Storm clusters
24
26. Knowage
§ Knowage is a Business Intelligence suite bringing innovative themes and engines.
§ Knowage offers a wide range of analytical tools:
§ Reporting
§ Multidimensional analysis (OLAP)
§ Charts
§ KPIs
§ Interactive cockpits
§ Geo-based business Intelligence analysis
§ Free Inquiry
§ masterdata management
§ Data mining and network analysis
§ Execution of external processes
§ ETL
§ …
25
27. Extended CKAN and Data/API BIZ Framework
§ CKAN is a data management platform that makes
data accessible by enabling the publication,
search, and consumption of datasets
§ CKAN is probably the most widely open data
publication platform used today
§ CKAN extensions has been developed in FIWARE
to enable:
§ Managing NGSI API queries as “dynamic” datasets
§ Assignment of Access Rights Policies to datasets
§ Managing Access Rights acquisition
§ Binding pricing to datasets (acquisition and access)
§ FIWARE Biz Framework components rely on
TM Forum Business Open APIs
26
Open APIs
• Catalog
• Product offering
• Product inventory
• Billing
• Party/Customer
31. 30
§ Goal: Noise monitoring
and sound event detection and
identification
§ Target customers: smart cities,
smart spaces, security
companies
§ Main features:
§ advanced and
innovative analysis using 3D
audio captures
§ monthly and daily readings
and statistics
32. 31
§ Goal: Turning Fleet Maintenance
into an exact science
§ Target customers: transport sector,
field service fleets, …
§ Main features:
§ Simple installation
§ Continuous mechanical analysis
in real time
§ Advanced Artificial Intelligence
Techniques for predictions
§ Real-time notification to
management and workshops
33. § Goal: Free livestock monitoring
§ Target customers: livestock farms
§ Main features:
§ Monitor free livestock using IoT
collars weared by each animal
§ Position, activity, inventory,
anomalies
§ Ecosystem with veterinarians,
livestock markets, etc.
§ Save money by early detection of
sick animals
§ SIGFox / LORA / 3G
32
34. § Goal: Remote monitoring
and optimized replenishment
of silos in farms
§ Target customers: farms and
feed suppliers
§ Main features:
§ patented 3D scanning
§ easy installation (5 mins)
§ no batteries (solar panel)
§ collaborative platform for
farmers and feed suppliers
33
35. § Goal: Non invasive osteoporosis
prevention
§ Target customers: Osteoporosis
concerned population
§ Main features:
§ Measurement of indicators for
bone mass creation (exercise, UV
radiation, calcium ingest…)
§ Daily monitoring of exercises
§ Bluetooth LTE
§ Attractive design
§ Gamification and engagement
34
36. • Common APIs:
ü FIWARE NGSI to start with
• Standard Data Models:
ü CitySDK and more, collaboratively
• Platform for Open Data/API publication
• Driven by implementation approach
100+ cities
22 countries
FIWARE: why (in Smart Cities)?
35
FIWARE NGSI and Context Broker
Technology has been selected to
become a CEF (Connecting Europe
Facility) Building Block
FIWARE has been recognized as
major contributor for a shared
IoT-Enabled Smart City Framework.
The initiative is led by NIST
37. FIWARE: why (in Smart Cities)?
§ Breaking vertical silos, building
a Context Info Management
layer that provides a holistic
picture of what is going on in
the city
§ Interoperability between
verticals
§ Merging data from:
§ vertical solutions
§ IoT networks
§ processing/analysis
§ Bringing the enablers to
process and analyze
right-time and historic context
data at large scale
36
38. FIWARE: enabling the Economy of Data
§ Enabling publication of
resources by third
parties
§ Ability to assign price
to the acquisition of
access rights and
definition of pay-per-
use schemas
§ Biz Framework
managing offering
based on Open
TMForum APIs
37
39. Now driving Common Information Models for the City
§ Portable Governance Solutions
§ Vertical solutions more easy to plug
or replace
§ Sharing of best practices between
cities made easier
§ Smart Cities as a market where it will
be more attractive to invest
38
40. FIWARE: helping Smart Cities in their transformation journey
39
1 2 3
• Vertical solutions (some
being IoT-enabled) bringing
efficiency in silos
• Historic data as open data
• Information still in vertical
silos, no global picture
Efficient and Open Support to
Data Economy
• city as a platform including
also 3rd party data enabling
innovative business models
• open and commercial data
enabling multi-side markets
4
• Horizontal platform gathering
“right-time” context info from
different vertical services
• Common information models
• Smart City Governance
Solutions
Truly Smart Unleashing Right-time
Open Data
• right-time context info
published to third parties
• authorization and access
control (API management)
• open innovation ecosystem
44. FIWARE case example: enriching car navigation through front-runner
smart cities using third-party data
43
• Car navigators can display context information
about available parking slots published by
cities or other data from third parties it has
acquired the right to access to
• The car can share speed info with the city if the
drivers agree and both get something in return
City of Santander
City of Porto
• Users can receive recommendations from
smart home systems (“do you want me to
switch on the heat before you arrive?”)
• Users may have paid for apps developed
around data and recommendations used
from the car (discount restaurants around)
45. 44
But we are not
creating just
technology ….
… but a sustainable
open innovation
ecosystem
55. FIWARE: Technology but much more
§ Mission: build an open sustainable ecosystem around public,
royalty-free and implementation-driven software platform standards
that will ease the development of new Smart Applications in
multiple sectors
§ Pillars:
54
eHealth
tourism
Transport,
Mobility and
Logistics
e-government
Smart
Energy Grid
…
the open source platform of choice for
developing smart applications
a meeting point where innovation happens and
users can experiment with the technology
activate funds and accelerate the business of
entrepreneurs using the technology
reach a global footprint, opening to regions
that share the same vision and ambition
support development of the community at local
level, bringing support, training, certification
57. FIWARE Foundation Mission
56
FIWARE Foundation
The FIWARE Foundation is a legal
independent body providing shared
resources to help to achieve the
FIWARE Mission by Empowering,
Promoting, Augmenting, Protecting, and
Validating the FIWARE technologies
and the whole Community around them.
Overall FIWARE Mission
To build an open sustainable
ecosystem around public, royalty-free
and implementation-driven software
platform standards that will ease the
development of new Smart
Applications in multiple sectors.
61. IoT would be an enabler, no barriers because of
complexity
60
Context Broker
Standard API
GET <Oauth token>
/V1/contextEntities/crop1/attributes/humidity
Reading the value
provided by a sensor
should be as easy as
reading an attribute of
an entity
“I don’t care what
low-level IoT protocol
is used”
“I should not need to
handle connectivity
with IoT devices”
62. Actuation on a device
should come as a side
effect derived from
updating the attribute
of an entity
PUT <Oauth token>
/V1/contextEntities/crop1/attributes/watering “on”
IoT would be an enabler, no barriers because of
complexity
61
Context Broker
Standard API
“I don’t care what
low-level IoT protocol
is used”
“I should not need to
handle connectivity
with IoT devices”