Technological Framework

Lead Partner:University of TilBurg

Objective of this Work Package is, together by all the cities, with all the developers, involving other actors where necessary, to package and consolidate existing practices and assets into a technological framework and a reference architecture that enables the effective transfer of smart city service components between cities, the uptake of the Pilots in Project Partner cities, and the “birth” of the CitySDK.

 

Special consideration is given to define divisions between general CitySDK components (like location information), domain-specific SDK components (like Public transport), and city-specific modules (eg. the part of additional software interface needed to make Helsinki City interface CitySDK-“compatible”). Common parts of the prior assets and different SDKs will be identified and shared (e.g. a location service API). The architecture will also involve the definition of a common data model (to define common entities like user, street, location, etc. in a common fashion).
A combination of a  service engineering methodology and open service technologies and standards  will  be used for the development of the SDK technological framework. Several open source Enterprise Service Bus implementations will be evaluated to choose the most appropriate as the backbone for connecting and integrating SDK city-based digital services to  support the pilots. The  SDK architecture will exploit the opportunities the  Service Oriented Architecture (SOA) offers to make  city-specific services available over the Web and allow the sharing and co-creation of digital services by engaging diverse cities.  In this way, proven public services can be tapped to offer a set of common services for all pilots’ to use and share. It also will be possible to create composable value-added public services thereby promoting innovation.

 

Also selected emerging new Internet technologies (both open source as well as commercial hardware-driven developments) will be assessed on their value for the SDK and if selected we will try to incorporate them into the SDK.

 

Special consideration is given to define the interfaces in the SDKs in a way that implementing the SDK – the Pilots in the Cities – will allow for open, further innovation of new smart city services beyond those Pilots by the Project Partners. This means for example 3rd party SME developers to develop their own iPhone apps for mobility or tourism using the city’s new CitySDK interface. These open interfaces and activities are already in place in several Partner cities. Especially Partners ESADE and ENOLL contribute to introducing open innovation requirements and best practices.

At the end of the project, all relevant project results will be packaged and consolidated into the CitySDK v1.0 for further dissemination and impact.

Comments are closed.