Monitoring and Data Transfer
Postal reception boxes in the social housing blocks
Innovative street lighting with free WLAN hotspots (T5.4)
Central data management system
ICT based central management and monitoring

Smart Data Platform

Munich Data management platform & smart services

General facts

Description & main goal

Smart Data Platform based on Siemens City Intelligence Platform (CIP) representing the central data hub for data provided within the project e.g. sensor systems, open data sources 

The Smart Data Platform is an open, secure and city-wide Platform, acting as a virtual data-backbone to collect, process, analyse, interpret, store and distribute accumulated city data in the domains of mobility, energy, urban living and crowd data. The platform acts as a virtual data backbone, thereby transforming “big data” into “smart data” and improving urban planning and the quality of life in urban spaces.

The main elements of the platform are:

  • A data gatekeeper function, to ensure compliance with City of Munich and EU data protection standards, giving residents a transparent view of how data is used.
  • A data processing platform on which data from existing sources is collected, classified and stored.
  • Software analytics modules to provide Artificial Intelligence analytics options that cannot be achieved with traditional IT methodologies
smartdata

 

Category
Platform
Deployment area
Munich
Involved actors and their role

City of Munich, IT department

Siemens Germany
Platform based on Siemens City Intelligence Platform (CIP)

Fraunhofer Gesellschaft - Institut für Arbeitorganisation
https://www.iao.fraunhofer.de

VMZ
https://www.vmzberlin.com/en/

University of St Gallen
https://www.unisg.ch/en

Key-contact person
Uwe Montag

Specific facts

Input dataset interfaces

Ongoing definition, depending on use case. E.g. REST API, Sensor data input etc.

Output dataset interfaces

TBD, ongoing

Analysing capabilities

Ongoing definition, depending on use case

Visualization capabilities

Ongoing definition, depending on use case

Operation and maintenance (by whom)

VMZ 

Stakeholder

VMZ, LHM, Fraunhofer gesellschaft (for Data Gatekeeper) 

Privacy related concerns (short description)

All individual use-case related privacy requirements need to be implemented into the Smart Data Platform flow chart model and agreed to by the data security office (not a concern but rather a to do)

Data (operation) security

Standard IT-deployment in secure environment

Number of data (information) sources involved

ongoing

Implementation status

In which phase is the project?
Implementation phase

What is the current implementation status/ what is the current activity step?
Roll out 
    
Have there been changes regarding the planned solution? Please outline any changes and reasons.    
Most relevant is that the complexity and scope of the Data Gatekeeper concept is higher than originally expected by all stakeholders. There is need to develop a detailed common understanding of the requirements and content to be implemented.
 

Complete 75%

Risk and challenges

Which risks & challenges is the project currently facing?
  • Risk of getting insufficient amount of needed raw data or general insufficient data to form reasonable solutions due to silo-structure of city departments and individual “concerns” to share data onto data platform.
  • Challenge of getting use-case owners to think innovatively and in a future oriented way about the Smart Data Platform, about using it as a tool to experiment with new city planning approaches and as a means to apply for additional funding.
Which are critical or seem invincible? Please provide a detailed description

Both risks and challenges mentioned above are critical: A Smart Data Platform on its own is not useful if it is not fed with the right data and challenged to analyse the right things. Both of these triggers are dependent on the open mind-set of the stakeholders and their willingness to look beyond today’s barriers.

Which previously identified risks and challenges have you managed successfully and how

Not applicable (first reporting period)

Lessons Learned and Recommendations

Which lessons learned can be derived up to this point from the implementation process?

A detailed project specification outlining project objectives and scope in written form helps to coordinate and focus all stakeholder’s (potentially different) perceptions from the beginning.

What could be done better in comparable future projects (what needs to be done and what needs to be prevented)?

Involve the relevant project participants who need to implement the project from the beginning (planning phase) to avoid handover deficiencies.

Next steps & To Do ́s

Please shortly outline the next steps planned for the implementation of the project. Are there additional steps planned due to occurred challenges? 
Regular face-to-face definition meetings with operational stakeholders. Stepwise approach to develop a common architectural understanding of the technical needs that allow to meet the original project scope between project definition and implementation phase. Sharpening topic definitions requires good communication as well as clear roles and ownership.
 

Implementation status

In which phase is the project?    
Implementation phase

What is the current implementation status/ what is the current activity step?    
Content preparation: Finalisation of Data Gatekeeper Concept including synchronisation of relevant implementation specifications for Smart Data Platform.

Is the implementation process on time or are there any derivations? 
The stepwise and parallel approach is time consuming and forces all involved stakeholders to work on various different levels of complexity at the same time.

Which project steps were performed since the last project reporting?

  • Proof-of-concept implementation for the end-to-end dynamic data exchange between a data source (smart home sensors) and the Smart City App for demonstration to Munich steering team; 
  • Final concept for the Smart Data Platform Architecture; 
  • Successful open-API definition and dynamic data flow between Securitas and Smart Data Platform. 

Have there been changes regarding the planned solution?
Current Data Gatekeeper description requires a complex verification and coordination of all described details and levels to meet the target group’s expectation.

Complete 85%

Risk and challenges

Which risks & challenges is the project currently facing?
  • Some partners working at another pace than others might create challenges in the overall project fulfilment regarding time, quality and replicability. 
  • A project partner might stop active involvement after having delivered a first implementation of a service without review and improve the first results to achieve a robust final (and replicable) version.  
Which are critical or seem invincible? Please provide a detailed description
Both risks and challenges mentioned above are critical, none of them seem invincible.
Which previously identified risks and challenges have you managed successfully and how
Not applicable

Lessons Learned and Recommendations

Which lessons learned can be derived up to this point from the implementation process?

Planning: 
A detailed project specification outlining project objectives and scope in written form helps to coordinate and focus all stakeholder’s (potentially different) perceptions from the beginning.

What could be done better in comparable future projects (what needs to be done and what needs to be prevented)?

Involve the relevant project participants who need to implement the project from the beginning (planning phase) to avoid handover deficiencies.

Next steps & To Do ́s

Please shortly outline the next steps planned for the implementation of the project.

  • Finalisation including quality gate for the Data Gatekeeper description
  • Finalisation of use-case definition for Energy and Mobility
  • Draft version of use-case for sensor-based solutions of the intelligent lampposts (after the open call has been processed)
     
Implementation status

What is the current implementation status/ what is the current activity step?    
Smart Data Platform is implemented and running. Data Gatekeeper concept is finalised.

Complete 100%

Risk and challenges

Which risks & challenges is the project currently facing?

Challenges:

  • Accuracy of measured input data provided by innovative sensors compared to reference data. 

Need to describe detailed analysis requirements within use case often overcharges stakeholders. 

  • (Still:) need to convince some data providers to deliver valuable data (concern of potential misuse of data).

Lessons Learned and Recommendations

Which lessons learned can be derived up to this point from the implementation process?
  • Regular synchronisation meetings with ALL stakeholders are important to avoid implementation misunderstandings.
  • Use Case discussions require expert input as well as political stakeholder agreements.
  • The necessity to technically implement an overarching Smart City Data Platform is accepted by all stakeholders. But the willingness to provide valuable input and to share existing and meaningful data, requires a good and common political understanding.
Next steps & To Do ́s

Please shortly outline the next steps planned for the implementation of the project.

  • Release Data Gatekeeper Concept
  • Finalise Smart Data Platform Analysis Dashboard (Mobility, KPI-Management, Additional Lamppost Sensors)
  • Complete Smart Data Platform description