1. Citadel…on the Move Kick-of Meeting 1 February 2012 Ghent, Belgium

2. Welcome and introduction of Partners Karl-Filip Coenegrachts (City of Ghent) Geert Mareels (CORVE)

3. The CITADEL team 1. CORVE (Flemish Region) – Geert Mareels (eGovernment manager), Hans Arents, Jessica Van den Dries, Katrien De Smet, Jan Godderis – External support by 21c (Julia Glidden, Susie Ruston) – WP1 and 2 lead 2. IS-practice – Hugo Kerschot – Project management 3. City of Ghent (Gent) – Karl-Filip Coenegrachts, Jelle Monstrey, Katrien Van Goidsenhoven, Peter De Bock, Bart Rosseau – WP5 lead 4. Issy Media (Issy-les-Moulineaux) – Eric Legale, Catalina Vasilescu, Sébastien Levy 5. Manchester City Council (Manchester) – John Keys 6. DAEM (Athens) – Yannis Ramfos, Ira Giannakoudaki, Dimitra Tsakanika 7. Intrasoft International – Christos Georgousopoulos, Vasilis Koutsiouris – WP4 lead 8. Alfamicro – Alvaro Oliveira, Jean Barroca, Jesse Marsh, Francesco Molinari – WP3 lead 9. IBBT – Shenja Van der Graaf, Bram Lievens – WP6 lead 10. ITEMS – Hervé Rannou, Sébastien Bachollet 11. ASTON University – Lim Ming 12. Fondation Euractive – Daniel Van Lerberghe – WP7 lead 13. Global Cities Dialogue –. 14. V-ICT-OR – Eddy Van der Stock, Raf Buyle, Ivan Stuer, Goedele Van der Spiegel – Supported by SOCITM: Martin Ferguson 15. ATC – Yannis Kliafas, Eva Jaho, Leonidas Kallipolitis

4. The CITADEL team: CORVE (1) Who are we? – Flemish E-government administration – Built data sharing platform between federal, Flemish and local administrations (MAGDA) – Initiators of the “Citadel Statement in December 2010 What’s our input in the CITADEL team? – Coordinator – Monitoring progress of the project, dealing with finances, reporting and administration.

5. The CITADEL team: IS-practice (2) Who are we? – Long-time experience in eGovernment and Information Society projects – Local, national, EU level experience What’s our input in the CITADEL team? – Day-to-day project management – Back-up for the Coordinator

6. The CITADEL team: Ghent (3) Who are we? – Department of Strategy & Coordination / Team e- Strategy What’s our input in the CITADEL team? – Experience with Open data on the local level (Apps for Ghent) – Ghent Living Lab

7. The CITADEL team: ISSY MEDIA (4) Who are we? Issy Media, a public-private company in charge of the communication and the development of ICT in the city of Issy-les-Moulineaux. → Print and Web publications, press relations, management of special events and billposting. → Co-ordinating the ICT-projects of Issy since 1995. What’s our input in the CITADEL team? → Pilot city in which public data from the cultural domain will be made available to stimulate the creation of shared services and applications. → Liaison with local government data providers to help make government data openly available for use. → End-user involvement and engagement to access collective knowledge and information → Promotion and dissemination of the project findings to other cities administrations/decision makers and SMEs, at local, national and international level

8. The CITADEL team: MCC (5) Who are we? Manchester Digital Development Agency (MDDA) is part of Manchester City Council and works with a wide range of local, national and international partners from the government, academic, business and community sectors. MDDA Co-ordinates the Manchester Living Lab and information society initiatives across the Greater Manchester city‐region including community-based digital inclusion, next generation access (NGA) broadband and smart energy projects. Overall our role is to support the regeneration of the city-region through the strategic and practical work of our technology-focused projects. John Keys – Project Officer What’s MDDA’s input in the CITADEL team? WP2 - Policy and Business Requirements T2.1 Current Situation Analysis – MCC will provide relevant information to the WP lead. WP3 – Open Access and Data Management T3.1: Management of Open Data Governance Groups – To set up a local OD Governance Group and coordinate the on-going work of the Governance Group. T3.3 Privacy Impact Assessments - To carry out a local Privacy Impact Assessment. T3.4 Semantic Framework Agreement – Contribute to the development of the Semantic Framework Agreement. T3.5 Open Data Commons Repository - To support the creation of the Open Data Commons Repository. WP4 - Innovation and Pilot Preparation T4.1 Scenario Development – Participate in the Internal workshop and host a scenario event. T4.2 User Requirements Gathering – To invite relevant stakeholders & host some of the meetings. T4.3 Technical Requirements Development - Revise Technical Specs and provide feedback. T4.4 Future Proofing with Geo-based technologies (IOT) – Support Co-ordinator of this task. T4.5 Template Mobile Applications Creation - Validate and provide Technology partners with feedback. T4.6 Testing and Review - Test & review the Template Mobile Apps. WP5 - Opening up the Pilot Sites T5.1 Deployment Planning – To support the development of the deployment plan. T5.2 Closed User Group - To lead on MCC’s service trial. T5.3 Open User Group – To be part of the approval committee & support the Open User Group. T5.4 Shared Services Validation – To select and adopt one of the test applications to demonstrate proof of concept. WP6 - Analysis and Evaluation T6.1 Evaluation planning – To support the development of the evaluation process and plan. T6.2 Collation of results – Collect and make available to the WP lead the evaluation data from MCC’s pilot. WP7 – Dissemination and Exploitation T7.3 Dissemination activities - To undertake agreed dissemination activities.

9. The CITADEL team: DAEM (6) Who are we? - City of Athens IT Company -Mission: to develop eGovernment systems so as to support Municipality of Athens and other local government organisations- clients by providing integrated IT services -Areas of expertise: software development & engineering, integrated IT solutions development, IT infrastructure development (networks, systems etc), personnel & end-users training, technical support & maintenance services, National/E.U co-funded projects What’s our input in the CITADEL team? – Initiating Open data at the local level, providing access to existing and suggesting more to become available – Open Governance groups and Service scenarios

10. The CITADEL team: INTRASOFT (7) Who are we? – Established in 1996. Member of INTRACOM Group of companies – We are established in 5 countries (Greece, Luxembourg, Belgium, Romania, Egypt), we have Long-term operations in 10 countries (Greece, Luxembourg, Belgium, Romania, Egypt, UK, Holland, Spain, Germany, Portugal), and projects in most EU Countries (UK, Lithuania, Latvia, Denmark, Portugal, Norway, Ireland, Sweden, Cyprus, …) – We have a Strong niche in public sector, specialising in services to EU Public Organisations (EU & National institutions), as well as in the provision of (i) application development, (ii) information and communication services, (iii) outsourcing and managed services, (iv) professional services – We are a multicultural team of 800 professionals operating out of 5 sites (Belgium, Luxembourg, Greece, Romania, Egypt), with a revenue of 90M in 2010 What’s our input in the CITADEL team? – Contributor in WP3: ‘Open Access and Data Management’ – Leader and major contributor in WP4: ‘Innovation and Pilot Preparation’ – Responsible for the development of the project’s portal in the context of WP7: ’Dissemination and Exploitation’ – Support in Piloting activities (WP5: ’Opening up the Pilot Sites’ & WP6: ’Analysis and Evaluation’ )

11. The CITADEL team: Alfamicro (8) Who are we? – ALFAMICRO was founded in 1983, with the objective to do research, consultancy and engineering services to support advanced re- engineering and integrated IT solutions. – Nowadays, Alfamicro is mainly devoted in applying Living Lab and User Behaviour Transformation methodologies to different sustainability scenarios, such as Energy Efficiency or the Smart Cities challenges of our times. – Alfamicro currently coordinates two CIP European Projects: Save Energy and PERIPHÈRIA. – At this moment, we are involved in three CIP Smart Cities Portfolio Projects: CitySDK, Citadel and PERIHÈRIA. What’s our input in the CITADEL team? – Alfamicro leads WP3 – Connection to the the Living Lab community namely through the European Network of Living Labs

12. The CITADEL team: IBBT (9) Who are we? – Interdisciplinary Institute for BroadBand Technology, a virtual research centre located in Flanders/Belgium – Mainly demand-driven research within 5 domains: Digital society, Future Health, Future Media & Imaging, Future Internet, Security – Develop and test environment: Living Lab expertise centre, Technical Lab – Stimulating entrepreneurship What’s our input in the CITADEL team? – WPLead WP6 – Assist the local pilots Provide methodology Coordinate and steer collation process Evaluation framework Validation

13. The CITADEL team: ITEMS (10) Who are we? – Expert SMEs Specialized in strategy, marketing and international think-tank fora in the area of ICT Market definition and opportunities, strategic studies for organization public and private Organization of Conference with international experts in Technology, Sociology, Economy – Hervé Rannou, CEO – Sébastien Bachollet, Consultant Manager What’s Items input in the CITADEL team? – WP2: Policy and Business Requirements T2.1 Current Situation Analysis – ITEMS will provide input to CORVE » Each of the Pilot Cities will provide information for their country. T2.2 Shared Standards Planning – CORVE and ITEMS will led the planning process with support from, ASTON and VIC. T2.3 Creating Common Standards/Guidance for Using Open Data and Mobile Technology to Create Public Services – CORVE, ITEMS, ASTON and VIC will lead the deployment of this task and will coordinate with all the other work packages as appropriate. – WP7: Dissemination and Exploitation T7.4 Market Analysis and business case development – ITEMS will support FEAP leader of this task 1 February 2012 Ghent, Belgium

14. The CITADEL team: ASTON (11) Who are we? – Dr Ming Lim - currently leading RFID Advanced Research and Lecturer in Logistics at Aston University (UK) What’s our input in the CITADEL team? – Data standardisation and management – Future proofing of geo-based technology (IOT) – Development of mobile application template

15. The CITADEL team: FOAP (12) Who are we? – Fondation EurActiv PoliTech – Part of the EurActiv Network – 1 st Online EU Policy Media Network – EurActiv Network in 15 countries in 15 languages – 609000 Readers What’s our input in the CITADEL team? – WP7 Leader

16. The CITADEL team: GCD (13) Who are we? – … What’s our input in the CITADEL team? – ….

17. The CITADEL team: V-ICT-OR (14) Flemish ICT Organisation – ICT-professionals of the local authorities in Flanders – Representing LOLA (worldwide) – EU-Partners: SOCITM (UK), VIAG (NL), KOMMITS (SE) Expertise & Focus – In-depth knowledge of Local Authorities Role: – Benchmarking & Standardization – Dissemination & mainstreaming

18. The CITADEL team: ATC (15) Who are we? – ATC is an IT solutions and services provider (SME), based in Athens, Greece – Sectors: Media, Banking, Retail sectors, Public sector organizations – Range of IT solutions: content management, human capital resource management, ERP, eLearning, web and mobile applications. – Expertise : 21 years in R&D and technology transfer projects What’s our input in the CITADEL team? Main involvement in WP4 Innovation and Pilot Preparation: T4.3: Technical requirements development T4.4: Future proofing with Geo-based technologies T4.5: Technical implementation of the template mobile applications

19. Agenda for today Hugo Kerschot (IS-practice)

20. The CITADEL project WP1 Project and Quality Management – CORVE and IS-practice – All partners WP2 Policy and Business Requirements – CORVE, IS-practice and all pilot cities (Gent, Issy, Manchester, Athens) – ITEMS, Aston, FEAP, GCD an V-ICT-OR WP3 Access data management – Alfamicro – All partners (ex. IBBT) WP4 Innovation and pilot preparation – Intrasoft – CORVE, all pilot cities, Alfa, IBBT, Aston, FEAP, GCD, ATC WP5 Opening up the pilot sites – City of Ghent – Other pilot cities, CORVE, Intrasoft, Alfa, IBBT, ITEMS, Aston, FEAP, ATC WP6 Analysis and evaluation – IBBT – CORVE, Pilot cities, Intrasoft, Aston, FEAP, V-ICT-OR, ATC WP7 Dissemination, exploitation – Fondation Euractiv – CORVE, IS-practice, Pilot cities, Intrasoft, ITEMS, GCD, V-ICT-OR, ATC

21. Agenda (1) 08.30hWelcome coffee 09:00h Welcome address and introduction of Partners Karl-Filip Coenegrachts (City of Ghent), Geert Mareels (CORVE) 09:20hAgenda of the day Hugo Kerschot (IS-practice) 09:25h Introduction to project administration and management Hugo Kerschot (IS-practice) 09:45hCitadel on the Move Vision Geert Mareels (CORVE) 10:00h CITADEL Vision: interactive session (first project deliverable) Susie Ruston/Julia Glidden (CORVE) 10.45h COFFEE BREAK 11:00h Introduction to WP2 – Policy and business requirements Susie Ruston/Julia Glidden (CORVE) 11:15hIntroduction to WP3 – Open Access and Data Management Jean Barocca/Jesse March (Alfamicro) 11:30hIntroduction to WP4 – Innovation and Pilot Preparation Christos Georgousopoulos (Intrasoft) 11:15h Introduction to WP7 –Dissemination and Exploitation Daniel Van Lerberghe (FEAP) 12:00hLUNCH

22. Agenda (2) 14:00h 2 parallel sessions: A) WP2 – Policy and Business Requirements (CORVE/V-ICT-OR) T2.1 – Current Situation Analysis D2.1 - Current Situation Analysis: Benchmarking report outlining the current state of open data policy and use in Europe. [due m2] T2.2- Shared Standards Planning – common approach D2.2 – Standard Development Strategy: Plan Team will follow to develop common standards [due m4] B) WP3 & WP4 – Open Access and Data Management (Alfamicro) Innovation and Pilot Preparation (Intrasoft) T3.1 - Management of Open Data Governance Groups D3.1 - Open Data City Charters Iteration 1: Common open data agreement for the project in the four pilot cities. [due m4] T3.2 - Citadel Open Data Charter T4.1 -Scenario Development D4.1 - Scenario Specifications: Report provide a baseline on the existing levels of smart service delivery across Europe, as well as outlining the potential service applications in transport and tourism fields [due m3] T4.2 - User Requirements Gathering D4.2 - User Requirements: This deliverable will document and consolidate the results from the organization of the workshops in the form of user requirements and needs. [due m6] 16:00h COFFEE BREAK

23. Agenda (3) 16:15hFeedback and action points from the parallel sessions - Reporting Visioning session and WP2 tasks (20min) Susie Ruston/Julia Glidden (CORVE) - Reporting parallel session WP3 (20 min) Jesse March (Alfamicro) - Reporting parallel session WP4 (20min) Christos Georgousopoulos (Intrasoft) 17:15hFormal “General Assembly” Contract and payments, Proposal for Consortium agreement, consortium bodies and chain of decision, Consortium, Other business: Next GA, …(Geert Mareels) 17:45hConclusions of the day: What’s next: agenda for next meetings, agreements on reporting and communication (15min) Geert Mareels (CORVE) Hugo Kerschot (IS-practice) 18:00hEND of meeting

24. Introduction to project administration and management (WP1) Hugo Kerschot (IS-practice)

25. Project administration and management Project Director Project Manager Timing

26. Overview WP1

27. Project management tools Project management plan (D1.2, due M3) Quality plan (D1.3, due M4) Gantt chart (planning tasks and deliverables/milestones) MyBBT online workspace Other communication tools: mails, conf. calls.. Consortium management structure (cfr. CA)

28. Partners

30. www.mybbt.be

31. Project management tools Project management plan (D1.2, due M3) Quality plan (D1.3, due M4) Gantt chart (planning tasks and deliverables/milestones) MyBBT online workspace Other communication tools: mails, conf. calls.. Consortium management structure (cfr. CA)

32. Consortium management structure Base on Consortium Agreement Reflected in PM plan Starting point: – General assembly (all partners represented, in GA terminology “project board”) – Day-to-day: Steering Committee (Coordinator and project management) – In between: Management board= Steering Com with all WP leads WP-lead is responsible for the management and the delivery of his WP

33. “CITADEL on the move…” VISION Geert Mareels (CORVE)

34. Challenge

35. TECHNOLOGY Facilitate development and use of smart mobile applications that can potentially be used anywhere by:  Deploying a mobile web approach (based on HTML5) that will allow applications to be used on most handsets  Addressing IOT/geo-location developments that provide advanced, value-added data sharing mechanisms INNOVATION Help unleash the full potential of Open Innovation Systems by:  Developing template mobile web applications that can be used by ‘citizen developers’ to create their own applications  Using the Living Lab methodology to help ‘citizen developers’ understand and use these templates DATA Empower ‘citizen developers’ to create the type of ‘smart city’ services they want and need by:  Creating and promoting the use of a common method for aggregating, transforming and publishing government data from differing sources into a more easily accessible format  Providing an easy way to link the use of mobile web app templates and "open access data" for use by developers and ‘citizen developers’ alike Objectives

36. Proposition Citadel…on the Move will use the Living Lab approach to engage end-users/citizens in the creation of innovative new mobile applications in the pre-agreed areas of transportation and tourism. In so doing, Citadel…on the Move will help to bolster the creation and use of shared, citizen- generated mobile applications by using open source / open platform technologies for applications that can be built using open access data.

37. To achieve key objectives, Citadel…on the Move will target three distinct communities of stakeholders – at the city, national and European levels - to help 1) co-create & beta test and 2) market & push: Open Data Communities Mobile Application Communities Smart City/Living Lab Communities Proposition

38. Pilot Pilot CityService AreaPotential Areas of Focus GhentTourismServices provided near transport hubs like railway stations Issy-les-Moulineaux ManchesterTransportEnvironmental data about communities and neighbourhoods Athens

39. Benefits of the Citadel…on the Move open innovation approach for cities are: Agility improves with opening up data to enable users' to rapidly and inexpensively create mobile applications that cover public service gaps and needs – innovation at the speed of life! Costs for delivering public services may be greatly reduced as citizens contribute talent to R&D for free Device and location independence enables users to access systems using a web browser regardless of their location or what ever handheld device they are using (e.g., iPhone, Android, Blackberry etc.) Scalability increased as all citizens can potentially create public services without the need for highly skilled programmers, plus innovations can be shared across cities Economic growth & innovation as the power of Open Data enables SMEs to create new market products Added value delivered through the sharing of new innovative services between cities – mobile service apps that work anywhere Outcomes

40. CITADEL Vision, Interactive Session Julia Glidden, Susie Ruston

41. T1.1 Project Visioning This task will focus on identifying the vision of what the project should achieve so the Team has a clear view of the future scenario to work towards. It involves the organisation of an interactive session during the project Kick-Off meeting. This session will try to draw out the expectations and help the diverse participating groups to make the initial steps towards a common understanding. This interactive session is expected to be repeated annually, so that the project vision is revisited and up-to-date addressing any future challenges. Participating Partners: CORVE will lead the visioning workshop at the kick off meeting and will ensure the vision document is updated annually. All partners will be required to participate in this process. ISP, as project support will use the vision document to help measure progress. FEAP as the Dissemination lead will use the output in WP7 to help describe the project to stakeholders.

42. Visioning Exercise “Imagine that it is 2015 and Citadel...on the Move has just finished. What are the desired project outcomes that you would need/expect?”

43. TECHNOLOGY Facilitate development and use of smart mobile applications that can potentially be used anywhere by:  Deploying a mobile web approach (based on HTML5) that will allow applications to be used on most handsets  Addressing IOT/geo-location developments that provide advanced, value-added data sharing mechanisms INNOVATION Help unleash the full potential of Open Innovation Systems by:  Developing template mobile web applications that can be used by ‘citizen developers’ to create their own applications  Using the Living Lab methodology to help ‘citizen developers’ understand and use these templates DATA Empower ‘citizen developers’ to create the type of ‘smart city’ services they want and need by:  Creating and promoting the use of a common method for aggregating, transforming and publishing government data from differing sources into a more easily accessible format  Providing an easy way to link the use of mobile web app templates and "open access data" for use by developers and ‘citizen developers’ alike Citadel Objectives

44. Key Outcomes of the Citadel…on the Move open innovation approach for cities are: Agility improves with opening up data to enable users' to rapidly and inexpensively create mobile applications that cover public service gaps and needs – innovation at the speed of life! Costs for delivering public services may be greatly reduced as citizens contribute talent to R&D for free Device and location independence enables users to access systems using a web browser regardless of their location or what ever handheld device they are using (e.g., iPhone, Android, Blackberry etc.) Scalability increased as all citizens can potentially create public services without the need for highly skilled programmers, plus innovations can be shared across cities Economic growth & innovation as the power of Open Data enables SMEs to create new market products Added value delivered through the sharing of new innovative services between cities – mobile service apps that work anywhere Citadel Outcomes

45. Visioning Exercise “Imagine that it is 2015 and Citadel...on the Move has just finished. What are the desired project outcomes that you would need/expect?”

46. Vision Exercise

47. COFFEE BREAK (up to 11.00h)

48. Intro to WP2,3,4 and 7

49. WP2: Policy and Business Requirements Susie Ruston

50. Objectives

51. Key Tasks

52. Timing

53. Responsibility Partner No.PartnerMan Months 1CORVE9 2ISP1 3GENT2 4IM1 5MCC1 6DAEM1 7INTRASOFT0 8ALFA0 9IBBT0 10ITEMS7 11ASTON7 12FEAP1 13GCD1 14VIC4.5 15ATC0

54. WP3: Open Access and Data Management Jean Barocco (Alfamicro)

55. Work Package LeadKey Contributors Timing Timing and Responsibility

56. Overview

57. Approach Stakeholder involvement in «opening up» and governance of Open Data Cyclic «application-pull» development path: datasets defined by needs Select a user-friendly data format tool to perform the clean up of unstructured data Involving citizens and businesses in dataset «clean-up» and maintenance Procedures and standards are formalised on an on-going, incremental basis

58. Outcomes Open Data Governance Groups formed in each pilot city with key stakeholders Open Data Agreements for each city and Open Data Charter for the Citadel network Impacts and protocols for a) privacy and security and b) semantic frameworks Open repository of datasets and access tools in the Citadel Hub Service Catalogue

59. Results Activities in WPs 4 and 5 will be enabled by the required underlying datasets Open Data «literacy» spread to city governments and citizens and businesses – Enabling role for innovative smart services – Awareness of privacy and other implications – Dataset maintenance as civic engagement City governments made aware of the significance and impact of Open Data

60. WP4: Innovation & Pilot Preparation Christos Georgousopoulos (Intrasoft)

61. Timing and Responsibility Work Package Lead Key Contributors Timing

62. Main Objectives This work package covers the operational and technical tasks needed to prepare the four city sites for the pilot deployment that will validate the Citadel...on the Move solution Key objectives : – Understanding the elements that make a city and its services ‘smart’ – Developing the Citadel solution taking into account the requirements and needs of the end users – Integrating the most appropriate technical elements to create an easy-to- use and access solution based on the work on Open Access and Data management (WP3) – Mobilising the key actors needed to deploy the pilot in real life setting in the four cities participating in the project (as per the work in WP5) The work package will be lead by INTRASOFT with the support of all the project partners.

63. Key activities T4.1 Scenario Development – creating a shared understanding among partners of what makes a city ‘smart’ through literature review and internal partner workshops – organising workshops in each of the pilot cities to create detailed service scenarios explaining and putting in context the type of data and technology to be used, to define the role of the users and ensure that the mobile service application templates meet their requirements and check that the presentation of the overall solution is both compelling and easy to use, irrespective of the platform where it is hosted T4.2 User Requirements Gathering – organising a number of consultation meetings where relevant stakeholders (mainly Living Labs staff and city administrators from the participating countries) will be invited to collect the necessary input that will drive the project developments. D4.1. Scenarios Specifications D4.1. Scenarios Specifications - M3 D4.2. User requirements D4.2. User requirements - M6

64. Key activities T4.4 Future Proofing with Geo-based technologies (IOT) – investigating the software adaptors and elements needed to deliver the ‘smart’ elements of the potential service applications as per the scenarios developed – identifying the appropriate IOT middleware to ensure that any newly developed service applications during the pilots utilize geo-based elements enabling the apps to be shared with other cities – exploring integration approaches for these innovative web-based apps to perform efficiently across pilot cities – exploring infrastructure needs against the current (and foreseeable future) IOT platforms in the market – facilitating the creation of future-proofed Mobile Web Application templates T4.3 Technical Requirements Development – detailing the technical requirements for the Citadel solution – addressing elements related to the technical integration and cooperation of the various technology components needed to develop smart mobile template applications for city services in the transport and tourism domains – exploring requirements for the practical deployment of the envisaged applications on multiple platforms – ensuring that interoperability is built into the process in tight collaboration with WP3 and WP5 – adopting a cyclic, iterative development process and enabling the project to incorporate user demands vertically throughout the data system D4.3. Technical Requirements D4.3. Technical Requirements - M8

65. Key activities T4.5 Template Mobile Applications Creation – Developing the template mobile applications to assist any citizen (incl. non-professional developers) in leveraging Living labs and Smart cities service delivery innovation – Providing working code consuming real available open data sources in the Citadel hub, to citizen developers under an open source license – Targeting a number of predefined application scenarios, working across more than one city making uses of mobile technology – Exploiting Open Source and Cross Platform technologies (HTML5, PHP, MySQL) to develop the template applications – Demonstrating modern devices technologies, such as Geo-location, use of Camera, Near Field Communication and QR codes T4.6 Testing and Review – Testing the Mobile Applications templates with the newly formatted data made available in the Citadel Open Data Commons – Opening up the templates for comments and refinements to the existing online innovation networks that have an interest in smart mobile apps D4.4.x Template Applications Iteration D4.4.x Template Applications Iteration - M12,16,22,30

66. General Concerns … Shifting of Tasks’ duration & deliverable deadlines – need an official confirmation by the Coordinator/EC Issue with Deliverable D5.4 of WP5 – leadership needs to be clarified

67. Contribution to project success Ensuring that project developments are based on real user needs Combining the work on Open Access Data, to provide the solution components (templates) to assist less technically able citizens (non-professional developers) leveraging Living labs and Smart cities service delivery innovation Future proofing results ensuring infrastructure needs, address the current (and foreseeable future) IOT platforms Contributing to a European open innovation environment providing solutions that will be based on open source and cross platform technologies and will harness geo-based technologies for the creation of new ’Smart City‘ services that can be used and shared across Europe.

68. WP7: Dissemination & Exploitation Daniel van Lerberghe (FEAP)

69. Timing and Responsibility Work Package LeadKey Contributors Timing

70. Overview

71. EurActiv Network: 15 countries + 15 Languages Work Package Lead

72. LUNCH

73. Parallel Sessions A) WP2 – Policy and Business Requirements (Room next door) B) WP3 – Open Access and Data Management & WP4 – Innovation and Pilot Preparation (this Room)

74. A1) WP2 – Policy and Business Requirements Creation of Deliverable 2.1 V-ICT-OR/SOCITM

75. D2.1 – Current Situation Analysis – Due M2 Benchmarking exercise to: Help understand the current situation in Europe around open data provision for innovation Learn about good practices in using government data Understand the problems that arise in its use Participating Partners: CORVE, plus VIC –SOCITM and GCD networks will lead this activity with input from ASTON and ITEMS. Each of the Pilot Cities will provide information for their country.

76. Scope Define open government data provision for innovation in local public services Help understand the current situation in Europe around open government data provision for innovation Drivers Policy Scope of open data Publication e.g. redaction, format, channels, marketing Learn about best practices in using open government data Stakeholders – Public bodies, private sector, social entrepreneurs Good practice examples and outcomes Understand the problems that arise in its use

77. Literature Review ScheduleWeeks -4 to -1Weeks 1-2Weeks 3-4 Literature discoveryExtract key materialDraft report SOCITM252 VICTOR2 CORVE2 GCD2 ASTON2 ITEMS2 Discussion Initial Sources Framework

78. Consult with Stakeholders Schedule Create database of survey participants Design and pilot survey Set-up and market online survey Analysis of completed returns Draft report SOCITM 2235 ALL PARTNERS PROG OFFICE2 Discussion See next slides

79. Discuss How important are the following drivers for open government data provision for local public services innovation in your country? [Rate each on a scale of 0 to 5] Political i.e. policy frameworks, political support Economic i.e. cost reduction, efficiency Social i.e. transparency and accountability Technological i.e. consumerisation of ICT (e.g. ubiquitous smartphones, internet access, etc.) and utility computing (e.g. apps, gps, etc.) Legal i.e. statutory or regulatory requirement(s) Environmental i.e. supporting environmental goals, carbon reduction etc. Other [please specify]

80. Discuss What legal or policy frameworks (if any) exist for open government data provision in your country? o national o local What is the scope of open government data provision (if any) in your country? o Public policy o Service areas - strategy and performance o Service areas – operational data

81. Discuss What guidance (if any) exists to support the publication of open government data in your country? o Title and source o What does this guidance cover?  redaction  format  channels  Other Exploitation of government open data : o How is open government data being exploited by stakeholders?  Public bodies, private sector, social entrepreneurs, other(s) [please specify]  Services - health, social welfare, planning, environment, leisure, etc.  Types – location-based; individual; family; community  Technologies – apps, gaps, etc. o Good practice examples and outcomes o Understand the problems that arise in its use

82. Discuss Exploitation of open government data : Please provide details of up to five good practice examples of open government data exploitation: – Location and organisation details – Purpose – Method – Assessment (using IBM 5-stage maturity model?) – Outcomes achieved

83. A2) WP2 – Policy and Business Requirements Creation of Deliverable 2.2 CORVE/ITEMS

84. Plan outlining the strategic approach the Team will take to develop common standards Methodology that will: Meet the needs of key stakeholders Ensure that only good practice is considered Generate flexible recommendations that can easily adapt with tech advances Key Questions to be Addressed: What relevant standards already exist What are the role and position of existing SDOs regarding Open Data issue What are the gaps in standards? Where does Europe need a common approach? What information does the project and pilot need to deliver to help define standards? How will common consensus be generated for standards? What is the next step? D2.2 – Standard Development Strategy– Due M4

85. B) WP3 – Open Access and Data Management & WP4 – Innovation and Pilot Preparation Jean Barocca/Jesse March (Alfamicro) Christos Georgousopoulos (Intrasoft)

86. WP3 – Open Access and Data Management T3.1 - Management of Open Data Governance Groups D3.1 - Open Data City Charters Iteration 1: Common open data agreement for the project in the four pilot cities. [due m4] T3.2 - Citadel Open Data Charter

87. C) WP4 – Innovation and Pilot Preparation T4.1 -Scenario Development D4.1 - Scenario Specifications: Report provide a baseline on the existing levels of smart service delivery across Europe, as well as outlining the potential service applications in transport and tourism fields [due m3]

88. Scenario No.xx Scenario Title: Scenario Description: Open Data Sets (Available) – – … Open Data Sets (To be Available) – – …

89. WP4 – Innovation and Pilot Preparation T4.2 - User Requirements Gathering D4.2 - User Requirements: This deliverable will document and consolidate the results from the organization of the workshops in the form of user requirements and needs. [due m6]

90. T2.1 Current Situation Analysis What kind of data can be “opened up” and if not, why? How to segment types of data (from transparency to operational services, from national to local)? What similarities exist between the data formats, what are the key differences? What are the key barriers to using open data for city service creation? What are the specific organisations that members states have been setup and what are their mandate ? Which existing open innovation ecosystems are currently using open data to develop mobile applications? What legislation exists in this area, are there new European regulations that could help?

91. COFFEE BREAK (up to 16:15h)

92. Parallel sessions: feedback and action points Reporting Visioning session and WP2 tasks(20min) Susie Ruston/Julia Glidden (CORVE) Reporting parallel session WP3 (20min) Jean Barocca/Jesse March (Alfamicro) Reporting parallel session WP4 (20min) Christos Georgousopoulos (Intrasoft)

93. “First General Assembly” Geert Mareels

94. AGENDA Contract and payments Proposal for Consortium agreement, consortium bodies and chain of decision Consortium Other business: Next GA, …

95. Contract and payments

96. Proposal for Consortium agreement Section 1: Definitions Section 2: Purpose Section 3: Entry into force, duration and termination Section 4: Responsibilities of Parties Section 5: Liability towards each other Section 6: Governance structure Section 7: Financial provisions Section 8: Foreground Section 9: Access Rights Section 10: Non-disclosure of information Section 11: Miscellaneous Section 12: Signatures

97. Consortium

98. Next GA

99. Conclusions of the day

100. What’s next: agenda for next meetings, agreements on reporting and communication (15min) Geert Mareels (CORVE) Hugo Kerschot (IS-practice)

101. Thank you!