OPEN & AGILE SMART CITIES A technical introduction
Sergio Garcia Gomez
Telefonica I+D.
FIWARE Smart Cities & Data Architect
OASC PRINCIPLES
Driven by Implementation
(procurement, projects, labs, accelerators)
Common APIs
(NGSI)
Data Models
(CitySDK)
Open Data
Platform
(CKAN)
EXISTING, OPEN, DE FACTO STANDARDS: SIMPLE, POWERFUL – AND DEMAND-DRIVEN
Supports the Digital Single Market
Global initiative (born in EU)
Driven by cities (working with everyone)
3 mechanisms (+ driven by implementation)
2+ cities/country (local collaboration)
1 year to implement (maturity / integration)
OASC Task Force (user-driven)
OPEN & AGILE SMART CITIES 1st WAVE
March 16, 2015 (Hannover)
31 cities
7
countries in Europe and Brazil
OPEN & AGILE SMART CITIES 2nd WAVE
September 22, 2015 (Tampere)
61 cities
12
countries in Europe and Beyond
OPEN & AGILE SMART CITIES 3rd WAVE
November 18, 2015 (Barcelona)
75 cities
15
countries in Europe and Beyond
OPEN & AGILE SMART CITIES 4th WAVE
February 2016 (Puebla, MX)
89 cities
19
countries in Europe and Beyond
LIST OF CITIES Australia Brisbane, Gold Coast, Springfield
Austria Graz, Linz, Salzburg and Vienna
Belgium Antwerp, Brussels, Ghent, Leuven
Bosnia and Herzegovina Mostar, Sarajevo, Tuzla
Brazil Olinda (Recife), Anapólis (Goiás), Porto Alegre (Rio Grande do Sul), Vitória (Espírito Santo), Colinas do Tocantins (Tocantins), Rio das Ostras (Rio de Janeiro) and Taquaritinga (São Paulo).
Croatia Dubrovnik, Sibenik, Split
Denmark Copenhagen, Aarhus, Aalborg and Vejle
England Bristol, Cambridgeshire, Leeds, Manchester and Milton Keynes
Finland Helsinki, Espoo, Vantaa, Tampere, Oulu and Turku
France Saint-Quentin, Valenciennes, Amiens, Arras
Ireland Dublin, Galway, Cork and Limerick
Italy Genoa, Milan, Palermo, Lecce, Ancona, Cagliari, Terni and Messina
Mexico Cuautla, León
Netherlands Amersfoort, Amsterdam, Drechsteden, Eindhoven, Enschede, Rotterdam and Utrecht
Poland Gdansk, Grudziadz
Portugal Porto, Lisbon, Fundão, Palmela, Penela and Águeda
Scotland Aberdeen, Dundee, Edinburgh, Glasgow, Inverness, Perth, Stirling
Slovenia Idrija, Koper
Spain Valencia, Santander, Málaga, Sevilla, Sabadell, Guadalajara, Murcia, Las Palmas de Gran Canarias
Open Data/Content approaches
Datasets
Existing Datasets (census,
geographical, tourism,...)
Historic Data (from sensors, events...)
Real Time
Vertical Systems (mobility, events...)
Internet of Things (sensors, Smart
meters...)
Media
Video streams (traffic,
surveillance..)
Audio (microphones),
speaches...
Applications
NGSI CKAN WEBRTC
OASC PRINCIPLES
Driven by Implementation
(procurement, projects, labs, accelerators)
Common APIs
(NGSI)
Data Models
(CitySDK)
Open Data
Platform
(CKAN)
OASC PRINCIPLES
Driven by Implementation
(procurement, projects, labs, accelerators)
Common APIs
(NGSI)
Data Models
(CitySDK)
Open Data
Platform
(CKAN)
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
Bus • Location • No. passengers • Driver • License 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
NGSI: Context from different sources FIWARE: Restful binding of OMA NGSI 9 and NGSI 10
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
Place = “X”, temperature = 30º
What’s the current
temperature in place “X”? Standard API
A sensor in a
pedestrian street
The Public Bus Transport
Management system A person from his smartphone
It’s too hot!
Notify me the changes of
temperature in place “X”
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
FIWARE Context Broker
IoT Agent-1
IoT Agent-2
IoT Agent-n
IoT Agent
Manager
create/monitor
FIWARE Backend IoT Device Management
NGSI API (northbound interface)
(southbound interfaces)
MQTT ETSI M2M IETF CoAP
OASC PRINCIPLES
Driven by Implementation
(procurement, projects, labs, accelerators)
Common APIs
(NGSI)
Data Models
(CitySDK)
Open Data
Platform
(CKAN)
Open Data Platform
De facto standard platform for open data in Europe and beyond.
Search & Discover Data: Search by keywords
Browse by facets
Explore data with previews & visualization
REST/JSON APIs to access data and metadata
Data Management for publishers Easy store & update of metadata and data
Plenty of extensions: harvesting, geographical information, data visualization….
OASC PRINCIPLES
Driven by Implementation
(procurement, projects, labs, accelerators)
Common APIs
(NGSI)
Data Models
(CitySDK)
Open Data
Platform
(CKAN)
From Metamodel to data model
NGSI Metamodel
NGSI data example
Entity • Entity Id • Entity Type
Attribute • Attribute Name • Attribyte Type • Attribute Value
Metadata • Metadata Name • Metadata Type • Metadata Value
1 n 1 n
Entity • urn:santander:123 • MeteoSensor
Attribute • temperature • float • 23.5
Metadata • Accuracy • float • 0.01
OASC Participation model
Entity • entityId • entityType: serviceRequest
Attribute • status • string
Metadata • location • string • WSG84
Attribute • serviceCode • string
Attribute • position • coords
…
= CitySDK Participation + NGSI model
OASC PRINCIPLES
Driven by Implementation
(procurement, projects, labs, accelerators)
Common APIs
(NGSI)
Data Models
(CitySDK)
Open Data
Platform
(CKAN)
Showcasing OASC
o Cities involvement and commitment to unleash real time data.
• Pilots, procurement, R&D actions
o Start-ups and development partners to develop solutions in various verticals and distil the data models to be shared.
Showcasing OASC
OASC cities
App 1
App 3
App i
City 1
City 2
City 3
City k
City n
City 1
City k
City 2
City 3
City n
Showcase 1
Showcase 1
Showcase m
Transference to Market
FIWARE Accelerator
Programme
Other Prototypes or
ServiceReady solutions
Shared Data Models
Next technical steps at OASC o Tools to define NGSI-based data models and and models repository
o Definition of data models. CitySDK first.
o DCAT AP to support harvesting / interoperability among open data portals. CKAN as reference implementation
o Management of access control to data resources and data marketplace
o Federation / harvesting of data portals
o Publication of open data resources
o Technical guidelines
o Rolling plan for Standardization (ETSI ISG)