1st Partner Meeting 21 February 2018

1. Sustainable Urban Mobility Action Cluster Deployment of New Mobility Services in a smart city context enabled by MaaS & CCAM 1st Partner Meeting 21 February 2018

2. Agenda of the meeting • Overview of working groups • Demanddriven first/last milesolutions • Multi-modal Transport & Logistics in Smart City • Multi-modal Traffic Management and Multi Modal Traffic information • Intelligent Speed Adaptation • Changing roles / business impact / regulation / governance • Solution DrivenMultimodal last mile: focus on parking

3. Agenda of the meeting Working group 1 – demand driven first/last mile solutions • Scope: • on demand / first mile & last mile / shared / combined / integrated mobility services for passengers • enabling technologies & infrastructure • societal benefits / challenges (as overarching theme) • not only urban but also rural • Objective: help local economies to get most of the existing system with the help by new technologies / services • More concretely: from pilot phase to viable business models • Knowledge sharing • learning by doing • learning from pilots • be sincere with the good and bad experiences • Next steps: • to create matrix / inventory of pilots, sort them by categories, to be used as knowledge base & sharing platform • Write a paper as starting document for concrete projects • Who is missing? Universities, mobile operators • Scale up solutions, fusethem. • Coordinator: Philip Meikle – Nexxus?

4. Agenda of the meeting Working group 2 – Multi-modal transport & logistics in smart city context • Objective: MaaS for freight • Scope: • urban and sub urban areas • combine freight and passenger routes, especially last mile • combined services. Goods (parcels), pharmaceutical, etc. • circulair economy, vertical farming/fresh logistics. • Organisations/expertise necessary: multimodal experts, automation, new business modelsand their impact on deployment, spin off forhealthcare sector, cities as test sides, logistic chain, citizens, fleetowners, SME’s, passengers and operators. • Coordinator: Daniëlle de Boer • Identify next steps: • Actions: matrix with all the modes and good practices. Gap analyses (feasible, identify what are the good). • Timeline: • Analyses: 3 months, • Draft proposal: 9 months, • Partners involvement: 5 months. • Meeting schedule: in September during ITS congress, physical meeting.

5. Agenda of the meeting Working group 3 – Multi-modal Traffic management and traffic information • 3 sub topics: • smart parking solutions: smart parking information, open parking data, complete package of options for P+R parking facilities. Make aninventarisationwhatalready is used in othercities and howcan we learnfromeachother. • ISA 2.0: enforcementsfor speed limits. Incentive toacceptation of ISA (remove speed bumpsto accept ISA). • Multimodalstategy and smart combining traffic information and handling strategies (e.g. howto deal with green priority services (how do you get a strategyfor green priority). • Which roles/organisations are required: city/regions • Partner search: OEMs, Neutral integrator, private sector involvement, nationalgovernment • Coordinator: not assigned yet. Preferably city/region drivenor align with other platforms networks like Eurocities, TM 2.0, C-ITS deployment platform.

6. Agenda of the meeting 4. Working group – Intelligent Speed Adaptation • ISA 2.0

7. Agenda of the meeting Working group 5 – Changing roles / business impact / regulation / governance • Objective: how can local authorities be prepared for innovation? • Which roles/organisations on the table: 1 city, 1 region, research institutes, industry. Missing: a national level authority. • Coordinator: Not assigned yet (Polis will be the contact point at this moment) • Next steps: sketchbook where the following stakeholders provide thoughts/inputs on the following topics:

8. Agenda of the meeting Working group 6 – Solution driven multimodal last mile: focus on parking • Objective: first and last mile solutions. • The role of parking in resolving first and last mile problems: • 1) locating parking facilities close to train/bus stations, also on the outskirts of the city (for the first mile transport) • 2) locating parkings in the cities (for the last mile mobility)  • 3) seamless integration of both types of parkings with public transport, taxi or mass shared transportations platforms (as shared bikes, scooters, electric cars) to enable building mobility services on top of parking & public/private (ride-sharing/hailing) transportation data.  • Parking bikes in countries where they are popular and massively used (like in Holland) is an issue that has to be resolved (to assure tidiness in the city). • Having one payment system for all means of mobility is of high importance to facilitate adoption of multimodal transport and increase users’ satisfaction.  • Chinese WeChat and Dutch OV chipcard payment system were mentioned as good benchmarks in this respect.  • suggested to deliver smart mobility solutions (in two selected cities), demonstrate vendor independency and teaming up with other SMEs interested in co-creating common standards and interfaces.  • All the smart mobility solutions should be citizen-oriented and address cities real problems (recognising city mobility needs/challenges as the first step in the process). • Organisations missing: cities • Coordinator: Marek Stawinski • Next steps: • 1) Define city problem scenarios and achievable (from timing and budget perspective) solutions. Action initiated by Eunice/Marek and reviewed by All. Delivery date: by 9th March • 2) Find communication means to reach out to cities. Proposed channel: Eurocities (responsible – Charlotte), OASC (Marek). Delivery date: by 9th March.  • 3) Communication with cities: week of 12th March • 4) Organise workshops with representatives of interested cities week of 25 April (possibly during the conference in Ljubljana)  • 5) Expand the problems scenarios & solutions with input from the cities and present during the next NMS meeting • 6) Identify two cities to implement agreed smart mobility solutions – in May  • 7) Deliver MVP of problems solutions in June/July