http://www.fiware.org

http://lab.fiware.org

Follow @FIWARE on Twitter!

FIWARE: Value proposition for Smart CitiesJuanjo Hierro

Telefonica I+D. FIWARE Coordinator and Chief Architect

juanjose.hierro@telefonica.com, @JuanjoHierro (twitter)

Cities are where daily life and businesses

actually happen …

1

Smart Cities are not simply about more efficient

municipality services but transforming Cities into

ICT platform enabling innovation local economy

growth and well-being

But … How can the Smart Cities ultimately enable local

economy growth and well-being?

2

ecosystemopen globalsustainable

Build

an

Ecosystem and platform: two tied concepts

3

Open Standard

Platform

ecosystemopen globalsustainable

Why an open standard Smart City platform?

Avoiding vendor lock-in is nice …

• Standard Southbound APIs for sensor providers

• Standard Northbound APIs offered to applications

• Portability across platform providers

• Interoperability of apps on top of different providers

… but more relevant is to engage a larger

community of developers

• True innovation

• More competition, leading to cost savings

Not any standard is enough

• Modularity (should not mean “take it all or nothing”)

• Allow different business models

• Non-intrusive, should live with the fact that many

city service systems come from third parties with

their own platform

4

A successful ecosystem is that one which creates the right

incentives to all stakeholders

5

Entrepreneurs, Developers

• Develop once for a large market

• Easily meet potential customers

• Marketing, promotion

• Ability to test with real data and

end users

• Simple yet powerful APIs that

accelerate product development

The Smart City

• Connect to entrepreneurs

• Put their data at work

• Bring new innovative services to

end users

• Be more efficient

• Social Reputation

Platform technology Providers

• Ability to “coopete”

• Connect to entrepreneurs: jointly

exploit the opportunities

ecosystem

open globalsustainable

The FIWARE Program

Goal: capture opportunities derived from the new wave

of digitalization of life and businesses

Strategy: Build an ecosystem that will work as catalyst

for capturing the opportunities. Lead standardization

in Smart Cities and IoT (Internet of Things)

Pillars:

• FI-WARE : a generic, open standard platform which

serve the needs of developers in multiple domains

• FIWARE Lab : a meeting point where innovation takes

place, an opportunities can be incubated

• : a program that funds developers and

entrepreneurs, and ignites roll-out of the ecosystem

• FIWARE Ops : the suite of tools easing deployment and

operation of FI-WARE instance nodes

• FIWARE mundus: reach a global footprint, opening to

regions that share the same vision and ambition

eHealth

tourism

Transport,

Mobility

and

Logistics

e-government

Smart

Energy

Grid

…

6

7

Why is FI-WARE relevant to Smart Cities?

Being “Smart” requires first being “Aware”

Implementing a Smart City requires gathering and managing context

information describing the current and historic “state” of the city

Context information refers to the values of attributes characterizing

entities relevant to city services, governance and third-party apps

8

Bus

• Location

• No. passengers

• Driver

• Licence plate

Citizen

• Name-Surname

• Birthday

• Preferences

• Location

• ToDo list

Shop

• Location

• Business name

• Franchise

• offerings

Context Information

City Governance System

City Services Third-party Apps

Context Management in FIWARE

The FIWARE Context Broker GE implements the OMA NGSI-9/10 API:

a simple yet powerful standard API for managing Context information

The FIWARE NGSI API is Restful: any web/backend programmer gets

quickly used to it

9

Application/Service

Bus

• Location

• No. passengers

• Driver

• Licence plate

Citizen

• Name-Surname

• Birthday

• Preferences

• Location

• ToDo list

Shop

• Location

• Business name

• Franchise

• offerings

Context Broker

NGSI API

FIWARE NGSI: Context from different sources

Context information may come from many sources:

• Existing systems

• Users, through mobile apps

• Sensor networks

Source of info related to a given entity may vary over time

10

Place = “X”, temperature = 30º

What’s the current temperature in place “X”?

NGSI API

A sensor in a

pedestrian street

The Public Bus

Transport Management

systemA person from his smartphone

It’s too hot!

FIWARE NGSI: Basic interaction

Context Producers publish context information by invoking the

updateContext operation on a Context Broker.

Context Consumers can retrieve context information by invoking the

queryContext operation on a Context Broker

11

Bus = “X”, location = (x, y)updateContext

Context Broker

Context Producer

Context Consumer

queryContext

FIWARE NGSI: Subscription to notifications

Context Consumers can be subscribed to reception of context information

complying with certain conditions, using the subscribeContext operation a

ContextBroker exports. Such subscriptions may have a duration.

The Context Broker notifies updates on context information to subscribed

Context Consumers by invoking the notifyContext operation they export

12

Bus = “X”, next_stop = “A”, arrived = “Yes”updateContext (context_info)

Context Broker

Context Producer

Context Consumer

(consumer1)

notifyContext (id, context_info)

Id = subscribeContext (consumer1,

condition, duration

)

FIWARE NGSI: Context Providers

Context Providers can be registered to the Context Broker as “holders” of

certain context information.

A Context Broker will invoke the queryContext or updateContext operations

exported by Context Providers whenever they are queried for, or asked to

update, context information they hold

13

Bus = “X”, location = (x, y)queryContext / updateContext

Context Broker

Context Provider

(provider-x)

Context Consumer

queryContext / updateContext

registerContext (provider-x,

registration_data, duration, id)

)

Integration with existing systems

Context adapters will be developed to interface with existing systems (e.g.,

municipal services management systems in a smart city) acting as Context

Providers, Context Producers, or both

Some attributes from a given entity may be linked to a Context Provider while

other attributes may be linked to Context Producers

14

queryContext (e1,

attr1, attr2)

Context Provider

queryContext (e1,

attr1)

Context Consumer

updateContext (e1,

attr2)

Application

Context Broker

System B

(e.g. Transport

system)

System A

(e.g. GIS, POIs)

FIWARE NGSI: “The SNMP for IoT”

Capturing data from, or Acting upon, IoT devices becomes as easy as

to read/change the value of attributes linked to context entities using

a Context Broker

15

Context Broker

NGSI APINGSI API

GET <Oauth token>

/V1/contextEntities/lamp1/attributes/presenceSensor

PUT <Oauth token>

/V1/contextEntities/lamp1/attributes/status

“light on”

Setting up the value of attribute

“status” to “light on” triggers

execution of a function in the IoT

device that switches the lamp on

Issuing a get operation on the

“presenceSensor” attribute

enables the application to get

info about presence of people

near the lamp

Integration with sensor networks

The backend IoT Device Management GE enables creation and configuration

of NGSI IoT Agents that connect to sensor networks

Each NGSI IoT Agent can behave as Context Consumers or Context

Providers, or both

16

FIWARE Context Broker

IoT

Agent-1

IoT

Agent-2

IoT

Agent-n

IoT Agent

Manager

create/monitor

FIWARE Backend IoT

Device Management

OMA NGSI API (northbound interface)

(southbound interfaces)

MQTTETSI M2M IETF CoAP

Open data publication

Once context information is gathered, a lot of useful

complementary FIWARE enablers can be used

17

Context Broker

Advanced Web-based UI (AR,

3D)

Data/Apps visualization

Big Data AnalysisComplex Event

ProcessingMultimedia processing

Context Processing and Analysis

18

Applications

Complex Event

Processing

(CEP)

Context Management

Processing and Analysis

BigData Analysis

(Hadoop- based)

Context

Broker

Programming of

rulesNGSI-9/10

NGSI

Context

Source

s

Simple Processing

(aggregation, averages, …)

Sensor2Things

NGSI IoT

Agents

FIWARE IoT & Context/Management altogether

IoT Backend Device

ManagementBackend

Applications

FIWARE NGSI-9/10

Simple processing

CEP

IoT-enabled

Context

Management

Backend

BigData

Analysis

ContextBrokerOther

sources

Gateway/Device

Platform GEs

Gateway/Device

Platform GEsGateway/Device

Platform GEsGateway/Device

Platform GEs

Native NGSI

IoT AgentNative NGSI

IoT Agent

19

Data analytics

20

Context

Broker

NGSI

Context

Source

s

Analysis

Query/Reporting

Data mining

Extract

Transform

Load

Open Data publication

21

Context

Broker

NGSI

Context

Source

s

BigData

Analysis

Ensuring Privacy, Security and Trust

22

Target Smart City platform

Smart city platform as

a Data/Knowledge Hub

Non-intrusive, open to

third parties

CKAN

Big Data

Context Broker

Ac

co

un

ting

& P

aym

en

t & B

illing

IDM

& A

uth

Short-term

historic

data

BigData

Processing

Data

Quering/Action,

Publish/Subscr

Open Data

publishingReal-time

processing

BI

ETL

RULES

DEFINITION

TOOL

OPERATIONA

L

DASHBOARD

KPI GOVERNANCE OPEN DATA PORTALS

Service

orchestrator

Context

Adapters

CEP

23

IoT Backend

Device Management

measures /

commands

IoT Broker & Config

Management

(from sensors to things)

IoT/Sens

orOpen Dataactuators

Media

streams

Real Time

Media

Stream

Processing

City

Services

GIS

Inventory

Specific Enablers

Generic Enablers

FIWARE major differential features

24

• Federation of infrastructures (private/public regions)

• Automated GE deploymentCloud

• Complete Context Management Platform

• Integration of Data and Media Content

Data/Media Context Mgmt

• Easy plug&play of devices using multiple protocols

• Automated Measurements/Action Context updates

IoT Services Enablement

• Visualization of data (operation dashboards)

• Publication of data sets/services

Data/Services Delivery

• Easy incorporation of advanced 3D and AR features

• Visual representation of context information

Advanced Web UI

• Security Monitoring

• Built-in Identity/Access/Privacy ManagementSecurity

• Advanced networking (SDN) and middleware

• Interface to robotsI2ND

FIWARE Lab: A working instance of FIWARE working as

“the meeting point” where innovation takes place

25

Entrepreneurs, Developers

• Develop once for a large market

• Easily meet potential customers

• Marketing, promotion

• Ability to test with real data and

end users

• Simple yet powerful APIs that

accelerate product development

App Customers and Data providers

• Connect to entrepreneurs

• Put their data at work

• Bring new innovative services to

end users

• Be more efficient

• Social Reputation

FIWARE Technology Providers

• “Coopetitive” approach

• Connect to entrepreneurs: jointly

exploit the opportunities

4,2 M€ promotion campaign

• Campus Party events

• Startup Weekend events

• Chambers of Commerce

• 870 K€ in prizes

100 M€ of funding devoted

to entrepreneurs in phase 3

of the FIWARE program

Building the FIWARE ecosystem: the vision

FIWARE Catalogue

creation of dedicated

GE instances

Use of Global shared

GE instance

FIWARE provider A

26

Applications

FIWARE provider B

Applications

ff

4,2 M€ promotion campaign

• Campus Party events

• Startup Weekend events

• Chambers of Commerce

• 870 K€ in prizes

100 M€ of funding devoted

to entrepreneurs in phase 3

of the FIWARE program

• 12 nodes in Europe

providing up to 3000+

cores, 16TB+ Ram,

750TB+ HD

• Creation of nodes in

Mexico (1000+ cores)

and Brazil

• Level 1 and Level 2

support for the nodes

• Showcases for

developers,

infrastructures, smart

businesses

FIWARE Lab: A working instance of FIWARE working as

“the meeting point” where innovation takes place

The FIWARE Accelerator Program

28

How can standard Smart City data models easing

common solutions be defined? The problem

Smart City apps can be ported from one Smart City to

another once their platforms provide the same set of

APIs, that’s why FIWARE brings a rather high value

Without standard data models, Smart City apps would

need to come with adapters that transform data made

available by the city so that it complies with the data

model handled by the app but that has proven to be

easy with OMA NGSI (overall if NGSI is at both ends)

Creation of standard Smart City data models would

allow to avoid performing this kind of adaptation and

make portability of Smart City apps across Smart City

platforms a pretty straightforward task

How creation of these standard Smart City data

models can be fostered?

29

How can standard Smart City data models easing

common solutions be defined? The solution

A “design by committee” approach would not be

the best approach:

• Such kind of approach has proven to be wrong in many

other standardization efforts in the past

• Who grants that the defined model is suitable for what apps

need and developers want to have?

we need a “driven by implementation” approach:

• Identify real applications that solves a real problem and

cities would like to see running in their cities

• Check what data model they have been designed to work

with and take it as input

• Carry out a “data curation” process targeted to extract

commonalities and polish the data model

You will end with a set of standard data models and

soon a portfolio of killer Smart City apps working!

30

How can standard Smart City data models easing

common solutions be defined? FIWARE

The FIWARE Accelerator program enables to identify

killer Smart City apps developed by entrepreneurs

• These applications can as basis for definition of a standard

set of Smart City data models

• FIWARE resources would be devoted to help coordinating

the data curation process

• Involvement in this process becomes also an incentive for

the entrepreneurs to join the program (“I want to influence

the standard so that my app can easily align with it”, “I want

to provide one of the first example applications”)

• There are 80 M€ for entrepreneurs that can be put at work!

Cities connected to FIWARE Lab will play a key role:

• Their data models will be contrasted/analyzed against those

coming from the apps and other cities

• They would get involved in the data curation process

31

Why FIWARE

Driver What is needed? What does FIWARE bring?

Technology Open, driven by implementation, specs(open source reference implemenation)

Sustainable investment over time

Open specifications backed by open source reference implementations (see[1], [2])100+ M€ of investment (2011-2016)

Experimental environment

Ability to experiment with real data coming from cities (not just open historicdatasets but real-time dat).Free Cloud capacity enablingentrepreneurs to test and host a permanent showcase of their applications.

15 cities (7 in Spain) already working onsetting up a connection to FIWARE Lab[3]3000+ cores, 16Tb RAM and 750+ Tb HD will be the free computing capacityprovided by the FIWARE Lab Cloud across 16 nodes distributed in Europe

Incentives forcreating theecosystem

Engagement of technology providers, entrepreneurs, data providers, customersFunding for first entrepreneurs joining theecosystem.Invesment in promotion and disseminationactivities

52 partners, 13 countries (just FIWARE)

100 M€ devoted to fund entrepreneurs in2014-2016. Additional opportunities in Horizon 2020.6,2+ M€ devoted to dissemination

Global footprint Helping entrepreneurs and technologyproviders to create opportunities not justin Europe but other regions (Latam, Asia and, why not, USA)

FIWARE Lab nodes in Mexico and Brazil.Conversations between EC and publicauthorities in Mexico and Brazil toexplore collaboration opportunities

[1] – http://wiki.fi-ware.org/Summary_of_FIWARE_Open_Specifications

[2] – http://catalogue.fi-ware.org

[3] – http://lab.fi-ware.org32

How the ecosystem is actually emerging: the

case of Smart Cities

Some cities already connecting to FIWARE Lab:

• Italy: Trento, Torino, Veneto

• Spain: Valencia, Sevilla, Málaga, Santander,

Logroño, Vigo, Lleida, Sabadell, …

• Finland: Helsinki, Espoo

• Netherlands: Amsterdam

• Portugal: Lisbon

• Ongoing discussion with other cities

FIWARE Challenge on Smart Cities:

• Launched end of October

• 300+ teams (individuals, startups, SMEs – few

researchers) applied to the challenge (ES, EN)

• 20 final teams run the final in CPBR 14

• quite amazing results!

33

http://fiware.org

http://lab.fiware.org

Follow @Fiware on Twitter !

Check latest videos at www.youtube.com/user/FIWARE

Join us!

34

FIWARE = advanced OpenStack-based Cloud capabilities

+ library of APIs that ease development of applications

35

Sustainability

ensured

Driven by

implementation

FIWARE Generic Enablers (GEs)

A FIWARE Generic Enabler (GE):

set of general-purpose platform functions available through APIs

Building with other GEs a FIWARE Reference Architecture

FIWARE GE Specifications are open (public and royalty-free)

FIWARE GE implementation (FIWARE GEi):

Platform product that implements a given GE Open Spec

There might be multiple compliant GEis of each GE Open Spec

One open source reference implementation of each

FIWARE GE (FIWARE GEri):

• Well-known open source license

• Publicly available Technical Roadmap updated in every release

Available FIWARE GEis, GEris and incubated enablers are

published on the FIWARE Catalogue

36

FIWARE Instances

Future Internet Applications run on top of “FIWARE Instances” that are

built by “FIWARE Instance Providers” upon:

• selection of FIWARE GEis (products) from the FIWARE Catalogue.

• assembly of selected FIWARE GEis with added-value components.

FIWARE Catalogue

FIWARE GE implementations

FIWARE Instance

37

Future Internet App

assemble…

added-value components

Domain-specific platforms = FIWARE + specific

enablers

FIWARE

38

GEs

SMART City

Apps

SMART Factory

Apps

SMART

Agrifood Apps

Domain

specific

enablers

FIWARE Ops: suite of tools for FIWARE providers

DeploymentDeployment of basic Cloud Hosting GEs and Monitoring Adapters in a FIWARE node

Federation Management

Federate a new FIWARE node within a given FIWARE instance (e.g., the FIWARE Lab)

Connectivity ManagementManage connectivity of services across FIWARE nodes of a FIWARE instance

Service Offer ManagementRegistration and deployment of additional Generic Enablers, Specific Enablers and

complementary Future Internet Facilities