FIWARE Extension to Latin America
ICT event
Lisbon, 20th October 2015
http://fiware.org
http://lab.fiware.org
Nuria de Lama
ICT Program Manager, Atos
FIWARE Collaboration Officer
nuria.delama@atos.net
FIWARE: Challenges & Opportunities
 FIWARE in a nutshell
 Value Proposition: FIWARE USP
 The Future: Sustainability
1
The wide context
2
Understanding FIWARE (Open Standard Platform)
(advanced OpenStack-based Cloud + rich library of Generic Enablers)
Driven by
implementation
Sustainability
ensured
3
FIWARE Generic Enablers (GEs)

A FIWARE Generic Enabler (GE):

FIWARE GE Specifications are open (public and royalty-free)

FIWARE GE implementation (FIWARE GEi):

 set of general-purpose platform functions available through APIs
 Building with other GEs a FIWARE Reference Architecture
 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
4
FIWARE major differential features
Cloud
• Federation of infrastructures (private/public regions)
• Automated GE deployment
Data/Services
Delivery
• Complete Context Management Platform
• Integration of Data and Media Content
IoT
• Easy plug&play of devices using multiple protocols
• Automated Measurements/Action Context updates
Apps
• Visualization of data (operation dashboards)
• Publication of data sets/services
Web UI
• Easy incorporation of advanced 3D and AR features
• Visual representation of context information
Security
• Security Monitoring
• Built-in Identity/Access/Privacy Management
I2ND
• Advanced networking (SDN) and middleware
• Interface to robots
5
Why an open standard platform is required


Avoid vendor lock-in:
• Standard Southbound APIs for sensor providers
• Standard Northbound APIs offered to applications
• Portability across platform providers
• Interoperability of apps on top of different providers
Larger community of developers (critical
mass, economies of scale)
• True innovation
• More competition, leading to cost savings

Not any standard is enough
• Modularity
• Allow different business models
• Integration with standard open data platform
• Non-intrusive (smooth integration with legacies)
6
Ecosystem and platform: two tied concepts
Open Standard
Platform
Sustainable Open
Innovation Ecosystem
7
FIWARE Lab: the “meeting point”
where innovation takes place
App Customers and Data providers
•
•
•
•
•
Entrepreneurs, Developers
•
•
•
•
Connect to entrepreneurs
Put their data at work
Bring new innovative services to end
users
Be more efficient
•
Social Reputation
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
 4,2 M€ promotion campaign
•
•
•
•
FIWARE Technology Providers
•
•
“Coopetitive” approach
Connect to entrepreneurs: jointly
exploit the opportunities
8
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
FIWARE Lab provides access to data
9
Funded by
the European Union
Accelerators’ Markets
Targeted
Ceed Tech
Legenda
Finodex
Smart cities (8)
Creatifi
Fractals
Content&Media
(9)
European
Pioneers
Frontier
Cities
FABulous
IMPAct
FI-Adopt
INCENSe
FI-C3
SmartAgri
food
FICHe
SOUL-FI
Finish
SpeedUp
Europe
Social&Learning
(4)
Energy&
Environment (4)
Agrifood
(4)
Transport
(3)
Manufacturing &
Logistics (1)
Health (4)
Source: FI-IMPACT Elaboration of Accelerators’ Data
11
The FIWARE Accelerator Programme: services
12
The ecosystem now
13
Open Source. Avoid vendor lock-in
You have the control
14
A live instance of FIWARE
available to developers for
free experimentation
Not only platform, tools…this is
powered by data!
15
Going from clusters to ecosystems
Cross-fertilization between sectors; avoid silos


Leading to a more powerful platform offering (based on common
functionalities; develop once and reuse as much as you can)
Then, translating the sectorial knowledge into domain-specific plafforms
16
Support and coaching
17
18
FIWARE support channels
 A Help/Contact page has been created on the
FIWARE website providing:
• Link to FAQ (Frequently Asked Questions) page
• Multiple contact mailing lists, each focused on a
given category of questions
 Mails sent to contact mailing lists
automatically generate a ticket on a troubleticketing system (JIRA)
 Tickets get assigned to some member of the
FIWARE community who takes care of
answering the email and close the ticket when
appropriate
 Handling of relevant technical questions are
moved to StackOverflow.com
19
Modularity; integration with legacies
Domain-specific platforms = FIWARE + specific enablers
SMART
Agrifood Apps
SMART City
Apps
Domain
specific
enablers
FIWARE
GEs
20
SMART Factory
Apps
Example: Smart City platform
RULES
DEFINITION
TOOL
OPERATIONA
L
DASHBOARD
KPI GOVERNANCE
Real-time
processing
Data
Quering/Action,
Publish/Subscr
BI
ETL
Inventory

Big Data
Service
orchestrator
Context Broker
Context
Adapters
CKAN
GIS

Open Data
publishing
Real Time
Media
Stream
Processing
Smart city platform as
a Data/Knowledge Hub
Non-intrusive, open to
third parties
IoT Broker & Config
Management
(from sensors to things)
IoT Backend
Device Management
IDM & Auth
City
Services
PORTALS
Accounting & Payment & Billing
Short-term
historic
data
CEP
BigData
Processing
OPEN DATA
measures /
commands
Specific Enablers
Generic Enablers
Media
streams
actuators
21
IoT/Sens
or
Open Data
Example: FIWARE for Smart Energy





FIWARE Sustainable Smart City Malmö, Sweden
FIWARE Smart Region Horsens, Denmark & Madrid
FIWARE X-border Virtual Utility, Aachen
FIWARE for the Energy Marketplace in Terni, Italy
FIWARE for Power management, Ireland
GE and DSE integration
22
Open source community designed to last and be open
to anyone who wish to actively contribute
Final model under definition. Starting proposal based on model of the reputed OpenStack community
•
•
•
•
Board made up of member
representatives (core members +
elected members):
•
Approves changes to
governance model
•
Elect officer of the
Foundation
Board
Foundation carries out Secretariat
and marketing activities and owns
FIWARE brand
Foundation
Technical Committee deals with
overall coordination
FIWARE Chief Architect and Lab
Coordinator elected by Technical
Committee
•
Leader and Architect of FIWARE
Chapters or FIWARE Ops elected by
active contributors in chapters
•
New FIWARE components can be
proposed and become part of the
FIWARE Core after incubation,
once they gain traction among the
wider community of developers
and subject to approval of
Technical Committee
new
members
core
election
growth
new
members
Technical Committee
FIWARE coordinator
& Chief Architect
Contributes
resources to
development
FIWARE
Lab
coordinator
coordinate
Chapter 1
Leader &
Chapter n
Architect
Leader &
Architect
FIWARE
Ops
Leader &
coordinat
e
Architect
23
FIWARE Core
(Generic Enablers)
Incubated
components
FIWARE: the way from a small market to a European market
EU market (2015)
352M mobile users just
for Western counties
(source: Statista 2015)
Spain (2015)
42,5 Million mobile users
(source: Statista 2015)
24
FIWARE: Commercial Support
25
Find out More!
 Introduction to FIWARE
• https://www.youtube.com/watch?v=PVS632As4Jw
 Introduction to FIWARE Lab
• https://www.youtube.com/watch?v=MXg5L_mjCWE
 FIWARE and SmartCities
• https://www.youtube.com/watch?v=yMPfGeGF5r8
26
New FIWARE videos: Use Cases!
https://www.fiware.org/developers-entrepreneurs/
 FI-Guardian
• https://www.youtube.com/watch?v=Kn6wHouHCzY


FoneSense
•
https://www.youtube.com/watch?v=034qW8KsSV8
SmallSignals
•
https://www.youtube.com/watch?v=imkta31qjFw
27
Join us!
http://fiware.org
http://lab.fiware.org
Follow @Fiware on Twitter !
28