emotion User Requirements Workshop 10/10/2006, London

Size: px
Start display at page:

Download "emotion User Requirements Workshop 10/10/2006, London"

Transcription

1 emotion User Requirements Workshop 10/10/2006, London 1 Agenda 09:00 09:15 Welcome and Introduction 09:15 09:35 General overview of the emotion project 09:35 09:55 Results of the user requirements analysis (WP1) 09:55 10:10 Formation of discussion groups 10:10 10:30 Impulse for discussion 10:30 10:50 Coffee Break 16:30 17:00 Discussion groups 17:00 17:15 Wrapping up of main outcomes 12:20 12:30 AOB, Closure of workshop 2 1

2 emotion - facts & figures Contract Type: Specific Targeted Research Project (STREP) Project Start: May 1, 2006 Duration: 24 months Project Costs: 3.45 Mio 3 emotion - facts & figures Consortium: ASFINAG, ATTC, HiTec, Tele Atlas, Telematix Service, momatec GmbH, OneStepAhead, interactive instruments, micks MSR, Softeco Sismat, Comune di Genova, AMI Azienda Mobilita e Infrastrutture, TIM Telecom Italia Group, Ministry of Transport in Slovenia, TSS Transport Simulation Systems (fact sheet, deliverables) 4 2

3 Status Quo of traffic information services Existing real-time information services for road traffic and public transport are in the majority of cases developed only for a special area and/or for only one mode of transport the integration of such services is still rather uncommon and primarily only realised in research projects in the form of a prototype 5 emotion - overall project aim The project aims at analysing the framework of a Europe-wide multimodal traffic information service in terms of organisational, legal, economic and technical issues in order to identify obstacles towards an implementation of such a service 6 3

4 emotion scope Organisational/Institutional, Legal and Economic Issues Technical Aspects Policies and Scenarios Organisational and Legal Framework Business Cases Standards Service Architecture Development of a Proof -of-the - Concept Validation of Framework Conditions 7 emotion - overall project aim The traffic information service the emotion framework is build for should offer real-time traffic information to road and public transport users, dynamic (and multimodal) routing services, additional travel-related services such as tourist information or hotel reservation via on-trip-devices like PDA/Smart Phones or in-carsystems 8 4

5 emotion scope device End User Service Provider Service Operator Content Provider 9 emotion scope device End User Service Provider Service Operator Content Provider 10 5

6 emotion scope emotion will analyse the processes to generate a information service and not to provide the service to the End User The nodes of the emotion network will be Content Providers (CP), Service Operators (SO) and Service Providers (SP) 11 emotion scope device End User Service Provider Service Operator Content Provider 12 6

7 emotion scope device End User Service Provider Service Operator emotion Application Service Content Provider 13 emotion scope The aim of the emotion application service is to handle all organisational issues of the network and to hold the emotion Catalogue The emotion Catalogue ( emotion Google ) holds information of the meta data of each node what node is able to deliver which information the technical aspects of every node 14 7

8 emotion scope device End User Service Provider Service Operator emotion Application Service Content Provider 15 emotion is not a multimodal service itself but gives the general framework for the introduction of such a services 16 8

9 Aim of this workshop To validate the results of our previous requirements analysis with members of the value chain for the emotion framework and to gather your point of view with respect to emotion. 17 Work Package 1 State-of-the-Art and User Needs Dr.-Ing. Andreas Kochs momatec GmbH 18 9

10 Content 1. Introduction 2. Service Chain 3. Existing Actors in Service Chain 4. Existing Services 5. Existing Content 6. General requirements and emotion services 19 Introduction (1) Tasks in WP 1: Review of current practice in European multi-modal real time traffic information service Analysis of stakeholder and actor needs and requirements and Definition of services, service chains and implementation approach 20 10

11 Introduction (2) emotion aims at the integration of existing and new end user services, service operators and content providers to realise any type of end user service on any end user device. Analysis of State-of-the-Art focus on: Types of services that are provided (information service, routing service, reservation service, location based services etc.), Types of on-trip devices that are used, Operational issues like identifying the institution that are involved in the services and their functions (content provider, service provider, etc.), Types of provided content, Concept of data providing, communication and other technical issues, Business concept of the services and pricing. 21 Service Chain (1) Content Provider Service Operator Network Operator Service Provider End user B2B B2C emotion is looking at the B2B-Service Chain: Content Providers (CP) provide raw data as basis for generation of information services Service Operators (SO) use the content to generate information services like map-based traffic information or routing Service Providers (SP) provide the information services to the end user Any actor can have more than one role in the service chain 22 11

12 Service Chain (2) Information request End User Service Provider device emotion network management service emotion data flow service Service Operator emotion data flow service emotion network management service Content Provider emotion network management service emotion Application Service emotion Framework 23 Types of Content Provider Road traffic routing service operator (static or dynamic routing) Navigation service operator (turn-by-turn-navigation for car) Public transport journey planner Multi-modal journey planner (comparison of public transport journey and car trip) Parking information service operator Road traffic information service provider (incl. weather data and POI etc.) In most cases the SO is at the same time CP or SP!!! Most important tasks of SO is presentation/visualisation of data Generation of interactive maps Generation of animation Generation of special service types like interactive voice response (IVR) service 24 12

13 Types of Service Operators Public/private map data provider (e,g, national map agencies, Tele Atlas) Public/private road network data provider (e.g. national road authorities, Tele Atlas) Public/private public transport network data provider (e.g. regional or national public transport operators) Public/private road traffic information provider (e.g. national traffic information centres) Public/private public transport data provider (e.g. regional or national public transport operators) Public/private parking information provider (e.g. local department or parking facility operator) Public/private weather data provider (e.g. national weather services or micks) Public/private POI data provider (e.g. national map agencies or Tele Atlas) 25 Types of Service Providers Often at the same time public CP like Traffic information centres (TIC) for Freeway traffic information service Municipal traffic department for local traffic incl. parking Local, regional and national public transport operators for public transport data Federal or national government for multi-modal information services Broadcaster like radio or television with services on different media like Radio or television Internet, PDA Call Centre or SMS, WAP, IVR-phone service Network provider like Internet provider for internet or PDA services Mobile phone network provider for PDA, mobile phone (SMS, MMS) services 26 13

14 Existing Services Routing and navigation services Dynamic car trip planning Turn-by-turn-navigation Traffic information services Traffic messages about congestion, road works, accidents, etc. Traffic flow information e.g. travel times, Level-of-Service Road conditions, weather information Parking information services Dynamic information about free spaces Public transport information services Dynamic public transport information (e.g. delays) Time table information and Journey planner Multi-modal journey planner Comparison of public transport journey and car trip POI-information services like Next gas station, hospital etc. 27 Existing Content Road network data (existing standards: GDF) Public Transport data (existing standards: TRANSMODEL (Europe), DELFI (Germany), NaPTAN/NPTG (UK)) Traffic flow data like traffic volume, density, velocity, travel times, LoS (existing standards: DATEX1/2, OTAP) Traffic messages (congestion, accident, warning etc.) (existing standards: DATEX1/2, OTAP, TPEG, Alert-C/RDS-TMC (Europe), SDEP (UK)) Weather data like temperature, wind speed, rain, fog, ice (existing standards:./.) Public transport schedule data (schedules, trip data) (existing standards: TRANSMODEL (Europe), DELFI (Germany), TransXChange (UK), JourneyWeb (UK)) Public transport event data(e.g. delays) RtigXml (existing standards: (UK), SIRI (Europe)) POI data (like gas station, hospitals, etc.) (existing standards:./.) 28 14

15 General Requirements and emotion services (1) General requirements: The emotion Framework shall enable the integration of every type of content or service The emotion services shall provide every functionalities to communicate the relevant types of data and information between the nodes in the emotion network The emotion Application service shall provide all functionalities for the administration and management of the emotion network The emotion Framework shall provide all required services and functionalities for data security, authentification, autorisation and accounting and payment and billing The emotion Framework shall provide the functionalities to administrate the emotion Catalogue (emotion Google) with all relevant metadata about content and services 29 General Requirements and emotion services (2) The identified emotion services are: Basic services used by different types of end user services Geocoding Service Positioning Service Mapping Service (Dynamic) Routing Service Event Notification Service (to realise PUSH-services) POI and Event Search Service Different types of information services Information Service for road traffic, parking and public transport (dynamic data) Public Transport Time Table Information Service 30 15

16 Thanks for your attention Dr.-Ing. Andreas Kochs Phone: momatec GmbH 31 AOB and closure of workshop 32 16