MaaS White Paper. Jukka Lintusaari

Transcription

1 MaaS White Paper Technical Issues for Deployment of MaaS Jukka Lintusaari MaaS Alliance AISBL Secretariat Avenue Louise 326 B-1050 Brussels! Tel : +32 (2) info@maas-alliance.eu!

2 h"ps://maas-alliance.eu/wp-content/uploads/sites/ 7/2017/09/MaaS-WhitePaper_final_ pdf

3 Activity pillars I. MaaS Requirements II. Policy & Networking III. Business IV. Research V. Communica?on Working Groups reports, White paper Networking with European Commission and Parliament, national & local levels (e.g. city networks) Define MaaS business case for stakeholders (Public Transport Operators, OEMS, IT-Tech companies, cities, etc.) and specific business case of the Alliance; networking events Support Alliance members new initiatives (H2020, etc.), collect & share information from ongoing initiatives, best practice observatory Communication materials (website, flyers, etc.) to generate interest in MaaS Alliance and disseminate about MaaS; share knowledge

4 Mobile Ecosystem Fundamentals Shared Vision & Use Cases Shared business architecture AcJon Plan (Interoperability & Architecture Roadmapping) Interoperable Services At Homes Digital Living Network Alliance (DLNA) promoter members Unlicensed Mobile Access (UMA) consortium members Rich Content Delivery in Convergence Today: Separare deliveries, businesses, services, technologies, products: NEC Personal Products, Ltd. Broadcast Delivery Fixed Delivery Mobile Delivery Active Companies in the Network Forum Broadcaster A wired and wireless interoperable network where digital content such as music and videos can be seamlessly shared through personal computers (PCs), consumer electronics (CE) and mobile devices in and beyond the home. Unlicensed Mobile Access (UMA) technology provides access to GSM and GPRS mobile services over unlicensed spectrum technologies, including Bluetooth and Fixed Operator Mobile Operator Content Future: Value, convenience and choices for consumer alternatives for service providers: Broadcast Delivery Broadband Delivery (Access) Operator Shared technical architecture Home Media Networking Mobile Delivery Content Content Key assets for convergence Enjoying Home media networking Digital Living Internet broadband connectivity: PC, laptop, phone Hi-Fi, Printers,TV, PVR, Game console, mp3 player, DSC, Videocorder Media VoIP Internet access, File Browsing, sharing images Printing music DLNA UPnP WLAN DLNA Digital Living Network Alliance UPnP Universal Plug n Play WLAN Wireless Local Area Network ( a.k.a Wi-Fi) videos Messaging 3 key enablers: - Wireless access - Automatic device discovery & control - Media format and transport compatibility November 14,

5 MaaS Core Use Cases My Mobility Factory enables connected user for Vehicle as you need it and when you need it A. Enabler connected vehicle or 1. Car sharing 2. Ride hailing B. Enabler connected road infra My Mobility Integrator My bookings Car shari ng Car Bike renting renting MyCustom Mobility ers Platform or CLOUD Connected user MY DATA Transport CUSTOMER Aps 1 Online Booking Rail Taxi Bus C. Enabler connected user My travel account Telecom My travel account is the king My bookings First mile transporta;on op;ons Apps Smart Traf)ic Business Development Long haul transporta;on op;ons Mul$modal travelling op$mized with one klick and integrated payment 3. Travel chains Last mile transporta;on op;ons Smart Traf)ic Business Development Payment Solution Technology Solution The company logos mentioned are only for descriptive purpose. Based on Frost & Sullivan & Tekes & University of Tampere material

6 Four Core Processes Customer Offering Booking Monitoring Se"lement Fully integrated in current transporta2on offering.

7 Customer Transportation Service Silos Offerin g Bookin g Monitor ing Se"lem ent Customer Train Offerin g Bookin g Monitor ing Se"lem ent Customer Offerin g Bookin g Monitor ing Se"lem ent Bus Taxi

8 Service Layer Separation Customer Offering Booking Monitori ng Se"leme nt MaaS operator Service provider

9 MaaS Subsystems and Actors Customer Offering Booking Monitoring Se"lement Apps layer Trip choice Trip purchase Customer comms Invoicing MaaS Operator Back-end System Trip formulajon Service offer: - Choices (speed, price, QoS etc) Customer id and data collecjon Issue travel docs Re-rouJng (if required) Service provider communicajon Se"lement calc: PenalJes etc Service provider payment Open API Open API Service Systems Product with a"ributes e.g. Price Route POIs T&Cs Trip confirmajon Capacity reservajon Re-rouJng Timetable monitoring Payment recepjon

10 Agreement by Leading Ecosystem Telecom Online Booking Transport Customer Rail Taxi Bus Apps layer Trip choice MaaS Operator Back-end System Service Systems Offering Trip formulajon Service offer: - Choices (speed, price, QoS etc) Product with a"ributes e.g. Price Route POIs T&Cs Booking Monitoring Se"lement Trip purchase Customer id and data collecjon Issue travel docs Trip confirmajon Capacity reservajon Customer comms Re-rouJng (if required) Service provider communicaj on Re-rouJng Timetable monitoring Invoicing Se"lement calc: PenalJes etc Service provider payment Payment recepjon Open API Open API Payment Solution My Mobility Integrator CUSTOMER My Custom Mobility Platform ers Car sharin g Technology Solution Car Bike renting renting The company logos mentioned are only for descriptive purpose. Based on Frost & Sullivan & Tekes & University of Tampere material

11 Conclusions MaaS ecosystem is much more than just the App Core use cases to be agreed and described Core MaaS processes to be agreed (offering, booking, monitoring, settlement) API management to be agreed MaaS platform(s), what does it mean? City-originated (transport) data is fundamental for MaaS success Acquisition of business partners to MaaS WGs to define APIs / interfaces for 4 core processes We are still in the learning phase: Dissemination, dissemination, dissemination

12 User Perspective for Current Mobility System Offering USERS - CiJzens, Entrprises MOBILITY OPTIONS AVAILABLE Walk routes Bike routes Bus system Taxi system Train system LogisJcs Mobility Silo Mobility Silo Private cars Mobility Silo Mobility Silo

13 Smart Mobility System Architecture ENTERPRISES CITIZENS Security VISITORS Mobility IntegraJon (eg MaaS) CITY RULES, REGULATIONS & PRACTICES Security Pedestrian solujons City bikes Shared cars MyData & IdenJty (payment) Smart HUB solujons & services (eg. smart node bridging trunk lines with feeding lines) City & region planning tools Mobility pladorms Sensors & robojcs Demand driven transport Taxi system Automated public transport Bus & tram system Train system Parking and park & ride strategy & solujons E-mobility and charging strategy & solujons IoT solujons (eg gateways) Private cars LogisJcs solujons Security TRANSPORT CODE OF CONDUCT Urban & regional data packages PosiJoning solujons (urban locajon awareness) Security KEY ENABLERS (eg HD 3D maps, locajon data sensor & city data)

14 API Framework for Subfunctions MaaS Operator Back-end System Service offer: - Choices (speed, price, QoS etc) Open API h"p://dupress.com/wp-content/uploads/2012/12/digital-age- TRANSPORTATION.pdf h"p:// Service Systems Product with a"ributes e.g. Price Route POIs T&Cs

15 ITS (MaaS) Data Sources "In God we trust. Everyone else bring data. Michael Bloomberg, Mayor of New York New data sources for innovative services and applications for the end users Road Traffic Traffic Flow Roadworks and Streetworks Incidents and Accidents Road Weather Parking Occupancy Facility Information Geodata Road network Other traffic infrastructure Street addresses Map data POIs Public Transport Timetables Stop Timetables Bus Location Route Planning Pedestrians and Cyclists Cyclist & Pedestrian Traffic Flow Route Planning

16 Online Booking Payment Solution Telecom My Mobility Integrator CUSTOMER My Mobility Platform Technology Solution Transport SMART INTEGRATED CITIES & COMMUNITIES SMART INTEGRATED MULTIMODAL TRAFFIC SMART VEHICLES Joint Mobility Architecture Joint Smart City Architecture Single market (Roaming & clearing) Joint Master Architecture System Interoperability Open data Smart Traf)ic Business Development

17

18 Mobility Ecosystem Interoperability Layers (examples from players acjve in Finland) Customer service packages including but not limited to MaaS services MAAS GLOBAL TUUP SITO Technology solujons & pladorms for services including but not limited to MaaS Pladorms SIEMENS FLUIDTIME Technology subsystems / modules PAYMENT (IQPAYMENT + many) ROUTING (DDS, VINKA + many)... Physical transportajon services including but not limited to current service providers CITY BUS L.D. BUS TAXI TRAIN New transportajon services CITY BIKES SHARED CARS...

19

20

21

22 MaaS Alliance WG Next Steps Piia Karjalainen MaaS Alliance Working Group work plan MaaS Alliance secretariat Autumn 2017, 17/10/17 Working group WG Users & Rules Leader(s) Main contributors Main focus Outputs by Dec 2017 (to be presented in plenary in Dec 2017) Krista Huhtala-Jenks & Jana Sochor rs.se; Maija Ahokas (MINTC) Maria Kamargianni (UCL) Sue Zielinski (Uni Michigan) Catherine Kargas (MARCON) Marius Macku (Uber) FIA CECRA George Hazel (MaaS Scotland) Josep Laborda (RACC) IRU Catapult? MaaS value creation for the end users (consumer rights, end user perspectives) The development and trends in regulation at EU level and in Member States Position paper on multimodal passenger rights Inventory of EU legislation affecting the MaaS development Outputs by June 2018 (to be presented in GA in June 2018 MaaS Bills of Rights WG Single Market WG Technology & standards Marko Javornik mtrade.com) Tommi Arola Koenraad Verduyn (PTV) CECRA Catherine Kargas (MARCON) Andy Taylor (Cubic) Andrea Renna (Skedgo) Marius Macku (Uber) Josep Laborda (RACC) Gregor Petri (Fluidtime) Silvia Magnalardo (PlusService) ATM Barcelona Ralf Frisch (PTV) EasyMile Andy Taylor (Cubic) Jukka Lintusaari (UTA) Filippo Logi (Siemens) Adrian Schonig (SkedGo) Marius Macku (Uber) Gregor Petri & Roman Pickl (Fluidtime) Daniela Vasari (PlusService) IRU Leaseurope Ecosystem and governance models: defining the business & governance model in bottom-up framework Exploring the trusted network concept in MaaS context Interoperability Interfaces & APIs Enabling the integration of added value services Standardisation & harmonisation Description of MaaS business models and their rules General technical principles in MaaS value chain Identify standardisation groups working with MaaS related questions Follow technology development and standardisation related to the MaaS system architectures Drafts for model contracts (resale agreements for transport services in a MaaS scheme, service level agreement, ) Based of description of busines models, secretariat will work t publish how to go MaaS guide / toolkit Specifications for open APIs and interoperability Participate in standardisation work and system development where the MaaS architecture ha special requirements

23 Jukka Lintusaari