2. The Open and Agile Smart Cities
(OASC) initiative
§ Common APIs à FIWARE NGSI to start with
§ Standard Data Models à CitySDK and more
§ Platform for Open Data/API publication
§ Driven by implementation approach
2
More info: http://
oascities.org
3. The Open and Agile Smart Cities
(OASC) initiative
§ Coopetion:
• Competition at platform level
• Collaboration: de-facto standards (APIs, models)
§ Digital Single Market for Smart Cities
• Portability
• Interoperability
3
4. FIWARE NGSI: the API for real-time open data
§ Gathering, managing and providing access to context information describing “what’s
going on” in the city becomes absolutely essential the more efficient management of
municipal services and enablement of 3rd party apps
§ A standard API for context information management becomes a cornerstone Pivotal
Point for Interoperability and Portability
4
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 SystemCity Services
City Services
City Services
City Services
City Services
Third-party Apps
standard API
5. FIWARE NGSI: the API for real-time open data
§ Simple yet powerful API enabing updates and access to context information from
different sources (not just IoT !) which may vary over time
• Existing systems dealing with management of municipal services
• Sensor networks (Internet of Things)
• Third-party smart city apps
§ Enables a key concept which was mising: real-time open data
5
Street = “X”, traffic = high
What’s the current traffic in
street “X”?
NGSI
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”
updates
updates
6. 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!
6
7. It’s time to execute!
7
OASC cities
App 1
App i
City 1
City 2
City 3
City k
City n
City 1
City 2
City 3
City n
App i
App r
App 1
Showcase 1
Showcase m
Transference to Market
FIWARE Accelerator
Programme
Other Prototypes or
ServiceReady solutions
Standard information models
13. ETSI Industry Specification Group proposal
§ Task Force on fast-track adoption of FIWARE NGSI
specifications evolution as de-facto standard API for
context information management
§ Task Force on specifications to be fulfilled by Data
Publication Platforms supporting open data publication
and/or monetization of data
§ Task Force on specification, curation, publication and
evolution of Cross-domain Data Models
§ Task Force on specification, curation, publication and
evolution of Smart City Data Models
13