CONTENTS 1. Why OASC? Martin Brynskov, Aarhus University, Chair OASC 2. OASC mechanisms, Juanjo Hierro, Telefonica, Chief Architect of FIWARE, OASC task force. 3. City of Antwerp, Prof. Pieter Ballon, Director Living Labs, iMinds, OASC task force 4. City of Tampere, Seppo Haataja, Director InnovaPon programmes, OASC Director 5. Hostabee, Vincent DemorPer, Hostabee, FI-C3 A16 6. The Porto FIWARE Ecosystem, Rui Costa, Ubiwhere 7. Q&A

1. OPEN%AND%AGILE%%
SMART%CITIES%
Ana%García%Robles,%ENoLL
Lisbon,%22>10>2015
#OASC
#FIWARE%%@FIWARE
@OrganiCity_eu
@openlivinglabs

2. Contents
1. Why%OASC?%MarPn%Brynskov,%Aarhus%University,%
Chair%OASC
2. OASC%mechanisms,%Juanjo%Hierro,%Telefonica,%Chief%
Architect%of%FIWARE,%OASC%task%force.
3. City%of%Antwerp,%Prof.%Pieter%Ballon,%Director%Living%
Labs,%iMinds,%OASC%task%force
4. City%of%Tampere,%Seppo%Haataja,%Director%
InnovaPon%programmes,%OASC%Director
5. Hostabee,%Vincent%DemorPer,%Hostabee,%FI>C3%A16
6. The%Porto%FIWARE%Ecosystem,%Rui%Costa,%Ubiwhere
7. Q&A

3. OPEN & AGILE
SMART CITIES
Martin Brynskov
@brynskov
Chair, Open & Agile Smart Cities
Coordinator, Danish Smart City Network

4. NETWORK OF NATIONAL
SMART CITY NETWORKS
Martin Brynskov
@brynskov
Chair, Open & Agile Smart Cities
Coordinator, Danish Smart City Network

5. SYNERGIES BETWEEN
SMART CITY INITIATIVES
Connected by
OASC

8. JANUARY 2015

9. • 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)
EXISTING, OPEN, DE FACTO STANDARDS:
SIMPLE, POWERFUL – AND DEMAND-DRIVEN

10. OPEN & AGILE SMART CITIES
Driven by
Implementation
(procurement,
projects, labs,
accelerators)
Common
API
(NGSI)
Data
Models
(CitySDK)
Open Data
Platform
(CKAN)

11. 1st wave · March 16, 2015
31
cities
7
countries in Europe and Brazil
OPEN & AGILE SMART CITIES

12. 2nd wave · September 22, 2015
61
cities
12
countries in Europe and beyond
OPEN & AGILE SMART CITIES

13. OPEN & AGILE SMART CITIES
2nd Wave · September 2015

14. 22nd Sept: OASC 2nd wave launch

15. 22nd Sept: OASC 2nd wave launch

16. STAKEHOLDERS
1: Cities
2: National networks of cities
3: International city networks
4: Projects & organisations

17. MAIN PRIORITIES
• Technical support
• Network support
• Fundraising
• “Angel City Investors”

18. ACTION PLAN
2015: Build-up
• Launch, director, secretariat
2016: Consolidation
• Support structure, SIGs
2017: Established
• Legal entity, office, finances

19. 2015-16
• September 1: Secretariat kick-off, Brussels
• September 22: 2nd Wave, Mindtrek, Tampere
• October 12-15: Open Days (REGIO), Brussels
• October 20-22: ICT 2015, Lisbon
• November 17-19: 3rd Wave, SCE, Barcelona
• January 21: CSC Conference, Brussels
• February 16-18: Smart City Expo, Puebla, Mex.
• …

20. 2015-16
• Secondment by “angel investor cities”
• Call for more angels
• 5-6 staff (2-3 FTEs) > 10-12 staff (5-7 FTEs)
2017
• Core staff and activities directly funded
• Secondment by “driver cities”
• 10-15 staff

21. TECHNICAL PRIORITIES
• Public OASC repository
• Open Data/API resources
• Showcases
• DCAT support

22. OASC MATURITY LEVELS
TARGET = HIGH
• Maturity Level 1: The city is still working at
strategic level. (No experimentation nor
deployment in production yet).
• Maturity Level 2: The city is in an
experimentation phase.
• Maturity Level 3: The city is moving
towards, or already at, a deployment in
production phase.

23. EXAMPLES (I)
• Maturity Level 1.0: The city does not have a strategic
plan regarding deployment of a cross-vertical smart
city platform but it aims at designing and implementing
one that is compatible with the adoption of OASC
principles
• Maturity Level 2.1: The city has a strategic plan
regarding deployment of a cross-vertical smart city
platform that is compatible with OASC principles and it
has designed a project (with planning and estimation of
resources) where it will run some experiments/pilots to
test the suitability of OASC principles as fundamental
pillars of their strategic plan. Funding for the project
may have not been secured yet.

24. EXAMPLES (2)
• Maturity Level 3.0: The city has designed a
procurement process with the intention to adopt a
smart city platform solution compliant with OASC
principles to be connected to existing verticals in order
to support overall management of city services and/or
publication of open data/APIs enabling development of
smart city apps
• Maturity Level 3.2: The city has already adopted a
smart city platform solution which is compliant with
OASC principles that has been deployed and is working
connected to existing verticals to support overall
management of city services and/or publication of
open data/APIs enabling the development of smart city
applications by third parties.

25. APPROACH
• Cities joining OASC will be assigned a
maturity level when they join which will be
made public
• This allows to monitor progress and provide
the most suitable support depending on the
maturity level
• Engagement of cities in different projects
to be incubated within the OASC Task Force
will depend on their maturity level

26. 1. Single point of entry for government.
2. Coordinated operational approach for open
data.
3. Investment plan for smart cities.
4. Research infrastructure for digital urban and
regional development.
5. Events
NETWORK SUPPORT
NATIONAL INITIATIVES

27. INVESTMENT PLAN
FOR SMART CITIES
NATIONAL
• Nation + Regional + Local funding
EU
• EFSI – Juncker Investment Plan: € 315b
• ESIF – Digital Single Market: € 21b
• ERDF – 5% for strategic initiatives
• Horizon 2020 – Research & Innovation, CSA
• Urban Innovative Actions – € 372m

28. ANGEL CITY INVESTORS
• Spearhead cities
• Leading initiatives
• Secretariat resources
• Open call now

29. Smart City Networks
Digital Single Market
Standards & Interoperability

30. Open & Agile Smart Cities:
Supports Digital Single Market
Digital Single Market (DSM) Open & Agile Smart Cities (OASC)
DSM supports the interoperability of new
technologies: The Free Flow of Data
initiative
OASC promotes interoperability and
portability of systems between cities, and
within cities, by adopting a shared set of
wide-spread, open standards and principles
The digital economy can expand markets
and foster better services at better prices,
offer more choice and create new sources
of employment.
OASC supports the development of
demand-driven innovative technologies and
services by transforming European cities and
society into digital platforms.
Industry stakeholders decide 'bottom-up'
in which areas to develop standards and
this is increasingly taking place outside of
Europe, undermining our long-term
competitiveness.
Being demand-driven, OASC boosts the
necessary development of open standards,
avoiding vendor lock-in and monopolisation.
A completed Digital Single Market will
help companies to grow beyond the EU
internal market
OASC supports the growth of European
companies beyond the EU internal market
through interconnecting national networks of
cities on a global level.
Source: OASC Task Force, ConnectedSmartCities.eu

31. STANDARDS
Concrete smart city standards related initiatives in Europe exist,
but need priority.
• Open & Agile Smart Cities (cities-driven, global), EIP-SCC
Memorandum of Understanding (industry-led, European), EIP-
SCC-02 + 03 (EIP Lighthouse + follower cities), SSCC-CG (joint
European standards initiative), Cities Standards Institute (UK-
based, global).
Public procurement in the digital age requires standards
• Procurement processes and regulations for cities have not
followed the pace of technological development. Hence,
the potential of agile co-creation, which is essential for modern
cities, is hampered, especially because of a lack of harmonized Pre-
Commercial Procurement (PCP) processes and standardised
tenders.
• An exemplary approach which aims to address this issue is the PCP
cofund action, e.g. SELECT for Cities, led by Forum Virium Helsinki,
now under grant preparation.

32. EXPERIMENTATION
OPERATIONS
City
Nation
World
Connected by
OASC
SELECT (PCP)
PROCUREMENT

33. OPEN & AGILE
SMART CITIES
Martin Brynskov
@brynskov
Chair, Open & Agile Smart Cities
Coordinator, Danish Smart City Network

34. http://oasc.org
http://fiware.org
Follow @FIWARE on Twitter!
!
OASC (Open and Agile Smart Cities) principles
Juanjo Hierro
OASC TF Board member. FIWARE Coordinator and Chief Architect
juanjose.hierro@telefonica.com, @JuanjoHierro (twitter)

35. OASC (Open and Agile Smart Cities) principles
1

36. OASC (Open and Agile Smart Cities) principles
2

37. You cannot be “smart” … if you are not “aware”
3

38. Being “Smart” requires first being “Aware”
! Smart City Application requires gathering and managing context
information, referring to values of attributes characterizing entities
relevant to the application
! NGSI brings a simple yet powerful API enabling access to context
information
4
Application
NGSI standard API
Bus
• Location
• No. passengers
• Driver
• Licence plate
Citizen
• Name-Surname
• Birthday
• Preferences
• Location
• ToDo list
Shop
• Location
• Business name
• Franchise
• offerings
Context Information

39. Different sources of context need to be handled
! Context info may come from many sources which may vary over time:
• Existing systems dealing with management of municipal services
• Sensor networks (Internet of Things)
• Third-party smart city apps
! Source of info will be transparent to applications accessing context info
5
Street = “X”, traffic = high
What’s the current traffic in
street “X”?
Standard API
A sensor in a pedestrian street
The Public Bus Transport
Management system Citizen’s car app or
smartphone
Notify me the changes of
traffic in street “X”

40. Different sources of context need to be handled
! Context info may come from many sources which may vary over time:
• Existing systems dealing with management of municipal services
• Sensor networks (Internet of Things)
• Third-party smart city apps
! Source of info will be transparent to applications accessing context info
6
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 Citizen’s
smartphone
It’s too hot!
Notify me the changes of
temperature in place “X”

41. City Services
Multiple system/apps can exploit context info
! Systems dealing with management of city services or third-party apps
can both consume and submit context information
! The overall city governance system can rely on context information
available (real-time and historic) to monitor and manage KPIs
7
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 AppsCity Services

42. A non-intrusive approach is required
! Capable to integrate with existing or future systems dealing with
management of municipal services without impact in their architectures
! Info about attributes of one entity may come from different systems,
which work either as Context Producers or Context Providers
! Applications rely on a single model adapting to systems of each city
8
Application/Service
Standard API
System A System B
attribute “location” attribute “driver”
Context Producer Context Provider

43. Connecting to the Internet of Things
! Capturing data from, or Acting upon, IoT devices should be as easy
as to read/change the value of attributes linked to context entities
9
Context Broker
NGSI APINGSI API
GET <Oauth token>
/V2/entities/lamp1/attrs/presenceSensor
PUT <Oauth token>
/V2/entities/lamp1/attrs/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

44. 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
10
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

45. OASC (Open and Agile Smart Cities) principles
11

46. How can standard Smart City data models easing
common solutions be defined? The problem
! Existence of a single API (FIWARE NGSI) reduces costs
when porting Smart City apps from one city to another
! 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 FIWARE 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?
12

47. 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 solve a real problem and cities
would like to see running in their cities
• Check what data models they have been designed to work
with and take them as input
• Carry out a “data curation” process where input data models
converge into a single common model
! You will end with a set of standard data models and
soon a portfolio of killer Smart City apps working!
13

48. How are standard Smart City data models going
to be defined within the OASC initiative?
! Leverage on existing work: CitySDK
! Leverage on initiatives like the FIWARE Accelerator
programme to identify killer Smart City apps
• These applications can serve as basis for definition of new
Smart City data models
• Involvement in this process becomes also an incentive for
the entrepreneurs to join identified initiatives (“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 in the FIWARE
Accelerator programme that can be put at work!
! Cities would 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
14

49. OASC (Open and Agile Smart Cities) principles
15

50. Open Data publication
16
Context Broker
NGSI
Context
Sources
Traditional “static”
historic data
NGSI standard
adapter

51. NGSI resources in CKAN
17

52. It’s time to execute!
18
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
App i
App r
App 1
Showcase 1
Showcase 1
Showcase m
Transference to Market
FIWARE Accelerator
Programme
Other Prototypes or
ServiceReady solutions

53. http://fiware.org
http://connectedsmartcities.eu/open-and-agile-smart-cities/
Follow @Fiware on Twitter !
Check latest videos at www.youtube.com/user/FIWARE
Thanks!
19

54. & OASC
Prof. Dr Pieter Ballon
Director Living Labs, iMinds

56. Three layers
Network-layer
Deploying a city-wide network
connecting multiple wireless technologies
Data layer
Providing an open data platform with a
real-time view on the city
User layer
Living lab approach to allow users
to interact with new technologies

57. General architecture
City of Things
Management Node
City of Antwerp
Fiber Network
City of Things
Gateway
City of Things
Gateway
City of Things
Gateway
City of Things
Gateway
Scattered across 70 locations
in city and harbor
Supporting multiple
wireless technologies
Pluggable set of sensors

58. Gateway architecture
City of Things Gateway
Controller
(CubieBoard 3)
Set of pluggable on-board sensors
Set of pluggable wirelessly
connected sensors
Zigbee
Communication
module
BLE
Communication
module
WiFi
Communication
module
DASH7
Communication
module
LORA
Communication
module
Sigfox
Communication
module

59. User behaviour

61. A*Sign
Innovating parking sign systems
CITY PROJECT
PERIOD
October 2015 to December 2015!
PROJECT
Real world user tests with the winner of Apps
for Antwerp who developed hard- and
software for a new parking sign system. !
CITY OF THINGS offers:
Businessmodel support, FIWARE integration, real-life Living Lab testing.!

62. City government system for
digital traffic signs
Digital traffic signs
Full planning & control system
Citizen service platform
New revenue opportunities
A*SIGN
APP
CITY WORKER
PLATFORM
WEB
CITIZEN REQUEST
PLATFORM
SIGFOX
GPS
NFC/QR
E-INK
BATTER
Y
ALARM
WEB
CITY CONTROL
NGSI
Real-time data
CITY OF THINGS

63. CONTACT DETAILS
Pieter Ballon!
Boerentoren, Antwerp!
www.cityofthings.eu!
Pieter.Ballon@iminds.be!
!
www.facebook.com/iminds!
ADDRESS:
WEBSITE:
EMAIL:
@iminds!

64. Open%Data%in%the%%
Tampere%Region%
%
Seppo%Haataja,%Director,%%
Open%Tampere%
%

65. Tampere%Aims%at%Transparency%
Central(administra-on(regula-on,(August(2012(
• “Tampere(obligates(its(units(to(open(data”(
Tampere(Mayor’s(policy(program(2013=2016(
• “City(increases(the(use(of(visualiza;ons,(open(data(and(e=services”(
• “Increase(ci;zens(ability(to(par;cipate(and(influence(decision=making”(
Tampere(city(strategy(2025(
• “The(informa;on(produced(by(the(city(is(open.”(
• “Opportuni;es(for(service(users,(service(providers(and(other(stakeholders(to(
par;cipate(in(service(development(and(decision(making(have(been(
improved.”(

66. Over%30%apps%&%services%
based%on%published%data%

67. Your%App%here!%
Traffic%informaEon%
providers%
Open data development in ITS Factory
Standard interfaces to raw data + option to use data
from providers
Raw%data%feeds%
Standard%Data%Interfaces%
Developer%Sandbox%
SIRI( DATEX=II( WMS/WFS( IFOPT( GeoJSON( Files(GeoRSS(TPEG(GTFS( Open311(
Public(
transport(
Traffic(
flow(
Parking( Maps( Fleet(Weather(
Traffic((
infra(
3D(model( Feedback(
Crowd=(
sourcing(
Open%data%
Open%Source(
Variable%data%business%models%
Variable%soJware%business%models(
re=use(
re=use(
re=use(
2.10.2015(MKu(

68. Largest%CiEes’%Sustainable%
Development%Strategy
Sustainable(Urban(Development(is(one(na-onal(EU(Structural(
Fund(program(2014−2020(emphasis.(
• Carried(out(by(Finland’s(six(largest(ci-es:(Helsinki,(Espoo,(Vantaa,(
Tampere,(Oulu(and(Turku(
• Ci-es(decide(the(contents(of(strategy(implementa-on(as(well(as(specific(
projects(to(be(financed.(
• Budget(about(100(M€(for(2014=2020.(
(

69. 6Aika:%Three%Focus%Areas
Open(Innova-on(Pladorms(
• Common(pladorms(for(ci-es,(ci-zens(and(companies(to(develop(and(test(new(
know=how(as(well(as(services(and(other(products.((
Open(par-cipa-on(
• Ci-zens(involved(with(the(development(of(decision(making(as(well(as(public(
services(and(other(ac-vi-es.(
• Open(and(smooth(mul-channel(customer(services(systems(for(all(ci-zens'(
groups.((
Open(data(and(interfaces(
• Ci-es(open(their(public(data(bases(for(public(and(private(users(and(harmonize(
their(data(interfaces.

70. OperaEonal%model%&%culture%
• Crea-on(&(deployment(of(models(
• Administra-ve(responsibility(&(
commitment(
• Opera-onal(culture(&(ahtude(
• Communica-ons(&(training(
Opening%data%
• Ac-va-on,(discussions((
• Instruc-ons(&(help(
• Clearing(house(opera-ons(
• Priori-zing(
• Documenta-ons(
CiEes,%ciEzens,%research,%companies%
• Data(processing(&(analyzing(
• Linking(public(&(other(data(
• Business(intelligence(&(predic-ons(
• Developing(new(services(
AcEvaEng%data%uElizaEon%
• Compe--ons,(hackathons(
• Community(mee-ngs,(trainings(
• App(galleries,(demos,(examples(
• Communal(developer(tools(
• Innova-on(pladorms,(business(
Data(
Big(/(enterprise(/(
my(/(other(data(
Data( Data( Data(Data(
Benefits%
• Savings(for(ci-es(
• New(services(
• New(business(
• Bejer(efficiency(
Architecture%principles%
• Open(specifica-ons(
• Open(APIs(
• Open(source(
• Common(standards,(harmoniza-on(
• Open(data(requirements(to(procurement(
process(
Data%distribuEon%
• Data(catalog(&(storage(
• License((na-onal(
recommenda-on)(
• API(management(
• Metadata(
6Aika:OpenDataTopProject

71. Open(data( Demand(
Supply(of(
services(
Innova-ons(
Metrics:(amount(of(
companies(and(revenue(
Metrics:(amount(of(
publica-ons,(degrees,(
patents,(applica-ons(
Metrics:(amount(of(data(
usage,(applica-ons,(
users(
Metrics:(amount(of(open(
data(and(interfaces(
Virtuous(circle(of(open(data(
Boosts:(
EU(direc-ves,(
state(and(city(
ac-ons(
Combining(data(
creates(new(
industries(
Open(data(creates(
new(opportuni-es(
Companies(create(
services(
People’s(needs(
create(demand(
Image couttery of atibodyphoto / freedigitalphotos.net.

78. The Porto FIWARE Ecosystem
Rui A. Costa (Ubiwhere, CEO)

79. Porto as a FIWARE-enabled City

80. THE COMPANY
2007
• Founded
2008
• New office at São João da Madeira
2009
• New office in Aveiro
• Turnover increased 145%
2010
• ISO9001
• NP4457
2011
• uBiLL Creation
• SME Innovation Network
2012
• Portugal’s 50 Hottest Startups
2013
• CMMI-Dev L2
• SME Leader
• Technology Fast 500 EMEA from Deloitte
• The European Seal of e_Excellence
• New office in Coimbra
• +1M€ Turnover
2014
• SME Excellence
• One of the best companies to work in
Portugal
2015
• CMMI-Dev L3
• Citibrain growing

81. Quality / Recognition

82. Team

83. SOLUTIONS

84. umeter.ubiwhere.com

85. 8
www.ubiwhere.com

86. 9www.livin.city

87. 10www.pervasivetourism.com

88. 11www.bikeemotion.com

90. 13www.playnify.com

91. www.citibrain.com

92. Ci#es&
Semi)Conductors&/&HW&
HW&Integrators&
IoT&Communica#on&
Carriers&
Middleware&
Data&Analy#cs&
Ver#cal&Pla@orms&
Apps&and&Services&
People&
Mobility& Environment& Payments& …&
Interoperability& FI)WARE&

93. Smart Cities Verticals
Horizontal&Pla@orms&
Quan#fied&Self&
Health&Monitor&
Connected&Home& Smart&Ci#es& Industrial&IoT&
Ac#vity&Trackers&
Sleep&Trackers&
AAL&Devices&
Smoke&Alarms&
Thermostats&
Mul#media&
Security&
Mobility&
Energy&
Ligh#ng&
Environment&
Retail&
Manufacturing&
Logis#cs&
Farming&
Parking&
Traffic&
Public&Transport.&
Urban&Logis#cs&
Self)Driving&Vehic.&
Fleet&Mgmt&
SoR&Mobility&
Shared&Rides&
…

95. Porto as a FIWARE-enabled City
Ubiwhere activities...
1. Making happen the Porto FIWARE Node
2. Improving the Quality of Life (QoL) in a Smart City
(through 75 connected sensors)
● Air Quality… 15 different sensors/parameters
● Noise
● Temperature
3. Making touristic POI “openly available”
4. Integrating the Porto FIWARE Node with the UrbanSense project/ platform
1. Taxis, Buses, Waste trucks
5. Integrating the Porto FIWARE Node with the VideoSensing project/ platform
6. Integrating the Porto FIWARE Node with the One.Stop.Transport project/
platform
7. Developing the MoodSensor iOS app
8. Water Metering Mobile App

96. Porto as a FIWARE-enabled City
Other Porto activities...
1. Developing a suite of applications to improve Security and Safety
2. Developing a suite of applications to improve Quality of Life and Environment
3. Improving the Efficiency of the Water Network through a Smart Metering
solution

97. THANK YOU!
+351 918 162 888
rcosta@ubiwhere.com
www.ubiwhere.com