The document provides an overview of the City Platform as a Service project which aims to provide an open urban data infrastructure to enable innovation in smart cities. The objectives of the project are to develop an open social city platform, deploy the platform as a service, empower citizens with their data, validate the platform with use cases, develop blueprints for adapting the solutions to other cities, and create impact in cities. Key achievements and metrics are provided for each objective, such as the number of use cases implemented, cities testing prototypes, and standards contributions made. Finally, the document discusses sustainability and deployment outlooks after the project's completion, with a focus on educating cities like Tokyo and potentially providing support for adoption.

1. City Platform as a Service – Integrated and Open
Project Overview
Ken Sakamura (YRP), Stephan Haller (BFH)
Project Coordinators
Final Project Review, Web Conference
February 21, 2019

2. Mission
February 2019 © CPaaS.io Project Consortium 2
Smart City
Innovation
Internet of
Things
To provide an urban data
infrastructure to enable
innovation in smart cities
Joining forces of EU and Japan
to make both regions globally
more competitive

3. Objectives
February 2019 © CPaaS.io Project Consortium 3
1. Develop an Open Social City Platform
2. Deploy the City Platform as a Service Solution
3. Empower the citizen to her data
4. Validate the platform with use cases providing public value
5. Develop blue prints for the adaptation and transfer of solutions to other cities
6. Create impact in cities

4. O1: Develop an Open City Platform
▪ Common functional
architecture
▪ Two instantiations (u2/FIWARE)
▪ Technology Readiness Level at
TRL 6-7 (prototype in relevant
to operational environment)
▪ Federation via APIs and
semantic integration
Success Criteria Target
Value
Actual
Value
# of OGD data sets interlinked with
IoT data
3 2
SPARQL access point in the
platform
available available
Technology Readiness Level (TRL) 6 6-7
# of third party applications built
on top of the platform, e.g., in
hackathons etc.
5 > 100
February 2019 © CPaaS.io Project Consortium 4
Achievements KPIs

5. O2: Deploy the CPaaS Solution
▪ Instances deployed in Japan
and Europe
▪ Federation via APIs and Linked
Data
▪ IoT Edge Computing
Framework (FogFlow)
▪ Data Quality Ontology
Success Criteria Target
Value
Actual
Value
# of deployed platform instances in
the Cloud
3 3
# of federations 1 2
# of credible demonstrations
showing redeployment
(edge/cloud) of analytics
functionality
3 3
Data quality annotations for all
queries
available data
quality
ontology
defined
February 2019 © CPaaS.io Project Consortium 5
Achievements KPIs

6. O3: Empower the Citizen to Her Data
▪ Personal Data Stores as main
mechanism
▪ Federation across instances
possible
▪ Base for Omotenashi hospitality
solution
Success Criteria Target
Value
Actual
Value
Dashboard easily usable by citizens
to control access to their data
available available
# of credible demonstrations
showing adaptive, context-
dependent data access
3 3
February 2019 © CPaaS.io Project Consortium 6
Achievements KPIs

7. O4: Validate the Platform & Use Cases
▪ Use cases implemented and
piloted in four domains
• Event management (Sapporo,
Utrecht)
• Water management (Amsterdam),
• Public transportation & Mobility
(Tokyo, Murcia)
• Emergency Medical Care (Yokosuka).
▪ Led to additional projects in
other cities
Success Criteria Target
Value
Actual
Value
# of use cases implemented and
positively validated by the City
Stakeholder Group
4 6
February 2019 © CPaaS.io Project Consortium 7
Achievements KPIs

8. O5: Blue Prints for Adaptation/Transfer
▪ Template for Smart City Blue
Prints developed
▪ Miura has adopted Yokosuka
Emergency Medical Care
application
Success Criteria Target
Value
Actual
Value
# of blue prints developed and
successfully transferred and
adapted to another region
3 Template,
3 Blue
Prints,
1 Transfer
February 2019 © CPaaS.io Project Consortium 8
Achievements KPIs

9. O6: Create Impact in Cities
▪ Useful innovations for cities
created – continued use
▪ Additional cities included
▪ Smart City Strategy Framework
▪ Standards (ETSI, AIOTI)
Success Criteria Target
Value
Actual
Value
# of cities testing prototype 3 8
# of cities interested in continued
operation of the platform beyond
the project
2 7
# of standards contributions 4 5
February 2019 © CPaaS.io Project Consortium 9
Achievements KPIs

10. Main Project Outcomes
February 2019 © CPaaS.io Project Consortium 10

11. Sustainability of Project Outcomes
February 2019 © CPaaS.io Project Consortium 11
Cities
• Platform & Toolboxes
• Standard Interfaces
• Strategy Development
• Transfer of Use Cases
• New Use Cases
Education
• Courses on Open
Data, Smart City,
IoT, Project
Management
Research Community
• Concepts & Tools
• Projects

12. Sustainability of Project Outcomes
February 2019 © CPaaS.io Project Consortium 12
Cities
• Platform & Toolboxes
• Standard Interfaces
• Strategy Development
• Transfer of Use Cases
• New Use Cases
Education
• Courses on Open
Data, Smart City,
IoT, Project
Management
Research Community
• Concepts & Tools
• Projects

13. Japanese Perspective of Deployment of Project
Outcomes, or Business Model
▪ Cooperation from city government offices is a MUST.
• Japanese partners have cultivated good cooperation with cities like Tokyo,
Sapporo and Yokosuka even before CPaaS.io (and added cities like Kochi
during the project).
➔ Focus on Tokyo as an important target.
▪ Public Transportation operators in Tokyo
▪ Important stakeholders: again in Tokyo
February 2019 © CPaaS.io Project Consortium 13
CPaaS.io Deployment

14. Adoption by Cities: Restrictions and what can
we do under such restrictions?
▪ Political process
▪ Electoral process
▪ Public opinion
1. Educate/show the way
2. Hand-holding if the cities want
to adopt
February 2019 © CPaaS.io Project Consortium 14
Restrictions How to Tackle

15. Tokyo: An Important Symbolic Target
Tokyo
▪ Capital of Japan
▪ 1/10th of the population
▪ Large economy
▪ High visibility
▪ An example which many regional government
offices in Japan emulates in terms of policies
and implementations
▪ So we focus on the ICT adoption in Tokyo
February 2019 © CPaaS.io Project Consortium 15

16. Tokyo: Educate / Show the Way
▪ Ken Sakamura has served as chair of a Tokyo
Metropolitan Government (TMG) committee to
guide the ICT adoption including the IoT adoption
for TMG
▪ The committee has produced policy suggestions
based on CPaaS.io results:
• Open Data,
• IoT
• etc.
Explained in detail in the 3rd city stakeholder meeting record in WP7
deliverables that explains the 3rd City Stakeholders Workshop during
2018 TRON Symposium (TRONSHOW).
February 2019 © CPaaS.io Project Consortium 16
Image: Flickr (Wally Gobetz)

17. Tokyo: Educate / Show the Way ⇒ Result
TMG has adopted the policy
recommendations from the committee.
▪ Open Data Catalog Site as recommended.
▪ Governor Koike stated at the 3rd city stakeholder
workshop session at 2018 TRON Symposium
(TRONSHOW) that TMG will use CPaaS.io along with
other technologies for future ICT adoption including
the use during 2020 Tokyo Olympic and Paralympic
Games
(Note: We don’t have monopoly. Remember the political, electoral,
and public opinion. Diversity counts here.)
Again, this is explained in WP7 deliverables.
February 2019 © CPaaS.io Project Consortium 17
Image: Flickr (Wally Gobetz)

18. What about Hand-holding for CPaaS.io
adoption?
This is covered as follows:
▪ VLED (General Incorporated Association "Vitalizing Local
Economy Organization by Open Data & Big Data“) offers
training for the regional government employees who
would like to pursue “open data”.
▪ Ken Sakamura of YRP and Noboru Koshizuka of UTokyo are
on the board of directors VLED. (Sakamura is the chair of
the directors).
▪ YRP and UTokyo have been helping VLED to offer such
trainings.
February 2019 © CPaaS.io Project Consortium 18

19. ODPT: Contest in Tokyo for the rest of Japan
▪ A few Japanese partners are the members of ODPT
(the association for Open Data of Public Transportation)
▪ It has organized a series of contests called Open Data
Challenge for Public Transportation in Tokyo.
▪ The data provision mechanism uses u2-based CPaaS.io
architecture.
▪ Again, we expect the public transportation operators in
the rest of Japan to follow the lead of these open data
activities of public transportation operators in Tokyo.
February 2019 © CPaaS.io Project Consortium 19

20. Summary of CPaaS.io Deployment Outlook in
Japan
February 2019 © CPaaS.io Project Consortium 20
▪ Educate/Show the way
▪ Hand-holding if necessary
▪ Whitepaper explains what has been achieved in Tokyo, Sapporo, and
Yokosuka.
▪ This may be called the deployment model (aka business model) under
the restriction of political/electoral/public opinion over city ICT policy
▪ In the end, it is up to the city government to decide, and we try to help
them make a wise educated decision.

21. Gracias Mulțumesc 謝謝 Paldies Eskerrik asko Dziękuję Mahalo ‫תודה‬ Go raibh maith agat спасибо Grazzi आभारी
Xin cảm ơn 감사합니다 நன்றி Köszönöm ‫مرسي‬ Ndiyabulela Grazia Tak Благодаря Aitäh Terima kasih Děkuji
Asante Diolch ‫شكرا‬ Takk Ďakujem Gràcies Kiitos Obrigado Teşekkür ederim Ngiyabonga Þakka þér Grazas
Tapadh leibh ขอบคุณ Faleminderit Ačiū Danke Merci Grazie Hvala Ευχαριστώ Dankon Tack Dank je Grazcha
…
Thank You
ありがとう
This document has been produced in the context of the CPaaS.io project which is jointly funded by the European
Commission (grant agreement n° 723076) and NICT from Japan (management number 18302). All information provided
in this document is provided "as is" and no guarantee or warranty is given that the information is fit for any particular
purpose. The user thereof uses the information at its sole risk and liability. For the avoidance of all doubts, the European
Commission and NICT have no liability in respect of this document, which is merely representing the view of the project
consortium. This document is subject to change without notice.
February 2019 © CPaaS.io Project Consortium 21