1. DYNAMO presentation slide 1 DYNAMO Dynamic Carpooling Service for people on the move Eurostars project reference: E! 5093 Project Overview Polivios RAXIS

2. DYNAMO presentation slide 2 Project facts  Program: Eurostars 3 rd cut-off  Reference: E! 5093  Acronym: DYNAMO  Full title: Dynamic Carpooling Service for people on the move  Budget: 800K Euro  National funding: 400K Euro  Countries participating: Greece, Romania

3. DYNAMO presentation slide 3 The Consortium  ATLANTIS Consulting SA. –Coordinator (Greece) –Expert in project management and online service provision  Integral Consulting R&D –Participant (Romania) –Expert in transportation telematics and GIS  University of Patras / Civil Engineering dept. –Subcontractor of ATLANTIS (Greece) –Expert in the transport domain (policies, services)

4. DYNAMO presentation slide 4 Project goals  Study –User “ wants ”, “ needs ” and “ concerns / barriers ” –Best practices for deploying the service and overcoming barriers  Develop –An online service that meets user expectations and circumvents non-technical barriers  Establish –A sustainable Business Model for the commercial deployment of a car pooling service

5. DYNAMO presentation slide 5 Project main objectives  Collect and analyze user feedback, identify NTBs and best practices  Design and implement the service –Spatial infrastructure, routing and (offer/demand) matching –WEB and mobile service  Verify the integrated system and deploy at (min) 2 test sites  Evaluate the service (technical, user acceptance)  Produce an effective Business Plan

6. DYNAMO presentation slide 6 Target market / groups  Commuters who make regular urban and/or interurban trips  Adults who make discretionary trips (shopping, entertainment, etc.)  Citizens with low income and no vehicle ownership –Students / younger generation –Unemployed

7. DYNAMO presentation slide 7 Main tangible / exploitable result (apart from the reports)  WEB service allowing users to define and offer or request trips for sharing  WEB and mobile interface to define start / end and intermediate trip nodes, based on predefined landmarks  Offer of a 3 + 1 (strangers) Level familiarity filter 1.Preferred users 2.Associated users (i.e. positive past experience or preferred users of own preferred users) 3.Members of a common affiliation or mini-pool (colleagues)  Matching based on rules (in order of hierarchy) 1.a) Full route, b) partial route / conjunction with Public Transport 2.a) 4-Levels familiarity filter, b) Preferences (users aged 25-30)  On acceptance of a shared ride, participants notified through E-mail/SMS

8. DYNAMO presentation slide 8 Project Timeplan

9. DYNAMO presentation slide 9 Project Work-Packages (1/2)  WP2 User Requirements & NTBs (Inteco) –Setting-up of User Group(s) –Analysis of user requirements –Identification of NTBs and best practices to overcome them  WP3 Service Design (ATL) –Use case scenarios, specs, architecture –Design of the service WEB site & of the mobile application  WP4: Development of Spatial Capabilities (Inteco) –Implementation of Map & Routing servers –Development of (complete/partial) route matching –Development of map / route display interfaces

10. DYNAMO presentation slide 10 Project Work-Packages (2/2)  WP5 Service Implementation (ATL) –Development of WEB and Mobile service UI –Development of Business Processes –Integration of service components  WP6 Service Deployment and Verification (ATL) –Deployment and verification at test sites –Service improvements, based on findings  WP7 Service Validation and User Appraisal (Inteco) –Technical & User Acceptance Evaluation  WP8 Dissemination / Exploitation (ATL) –Planning, promotion material, events, commercialisation agreement

11. DYNAMO presentation slide 11 Project Deliverables (1/2) Deliverable Month due StatusPartners D1.1: Project internal mailing listM1 Jul 2010 Finished ATL D1.2: Guidelines for reportingM2 Aug 2010 Finished ATL D1.3: Project Meetings (agenda, list of participants and minutes) Ad hockATL (Inteco) D1.4: Progress Reports (every 6 months) Spring, autumn ongoing ATL (Inteco) D2.1: Report on User Requirements and NTBs M8 Feb 2011 ongoing Inteco (ATL) D3.1: Report on use case scenarios & functional specs M10 April 2011 - ATL (Inteco) D3.2: Service Architecture and Design M13 July 2011 - Inteco (ATL) D3.3: Verification PlanM13 July 2011 - ATL

12. DYNAMO presentation slide 12 Project Deliverables (2/2) DeliverableMonth due Stat Partners D4.1: Spatial prototype M20 Feb 2012 - Inteco D5.1: Integration Discipline M17 Nov 2011 - ATL D5.2: Prototype ready for deployment M20 Feb 2012 - ATL (Inteco) D6.1: The deployed and verified service for the test site M23 May 2012 - ATL (Inteco) D6.2: Verification testing results document M24 June 2012 - ATL (Inteco) D7.1: Evaluation Framework M26 Aug 2012 - Inteco (ATL) D7.2: Consolidated report on evaluation M30 Dec 2012 - Inteco (ATL) D8.1: Dissemination Plan M12 June 2011 - ATL (Inteco) D8.2: Project Website M4 Oct 2010 ongoin g ATL (Inteco) D8.3: Project identity & promotion (leaflet, presentation, brochure) M15 Sept 2011 - ATL (Inteco) D8.4:Commercialization Agreement M24 June 2012 - ATL (Inteco)

13. DYNAMO presentation slide 13 M1-M13 Deliverables DeliverableMonth dueStatusPartners D1.1: Project internal mailing listM1 Jul 2010 Finished ATL D1.2: Guidelines for reportingM2 Aug 2010 Finished ATL D1.4: Progress Reports (every 6 months) Spring, autumn ongoing ATL (Inteco) D2.1: Report on User Requirements and NTBs M8 Feb 2011 ongoing Inteco (ATL) D3.1: Report on use case scenarios & functional specs M10 April 2011 - ATL (Inteco) D3.2: Service Architecture and Design M13 July 2011 - Inteco (ATL) D3.3: Verification PlanM13 July 2011 - ATL D8.1: Dissemination PlanM12 June 2011 - ATL (Inteco) D8.2: Project WebsiteM4 Oct 2010 ongoing ATL (Inteco)